Great news. It's always worth reaching out to the developers for issues like this that we are unable to solve. It didn't even cross my mind to compare the iNav resource assignments with the Betaflight ones which is something we could have easily done if we'd thought about it, but at least by raising it as a bug it gets fixed at source.

It looks like Mike has already merged the change back into the master trunk so the next release of Betaflight should have it fixed. In fact, you may find that it's already fixed if you were to re-flash any of the Betaflight 4.1.x targets through Betaflight Configurator because the unified targets don't seem to follow the normal release procedure. I think anything that gets merged to the master trunk immediately gets used by Betaflight Configurator when it asks if you want to apply the custom defaults after flashing.