Untranslatable fields saving to main language rather than being readonly

Currently, a field that’s untranslatable and being watched in a secondary language is readonly. Even though I do know that behavior, I tend to often be confused by those disabled fields that “shouldn’t” be; is even worse for the final users who don’t know what’s going on under the hood.

It would be nice if untranslatable fields could simply update the original language on save, maybe with a prop in the blueprint to control this behavior ? (translate all languages (current translate: true), update main from all languages (new feature), update only from main language (current translate: false))
There’s many cases where it is disturbing to have a disabled field in a secondary language since the value is globaly the same (a price, a set of related pages, tags, basically most non-text fields).