Your logic is sound, although I can't really imagine anyone adopting this scheme.
Actually, I would take it much further:
Instead of code being stored as a plain text file, store an abstract syntax tree in some binary form. Then all indentation, whitespace, keywords -- in fact, practically the entire syntax -- could be defined according to your preferences, while maintaining full interoperability with fellow developers.
Of course this would require an editor/IDE specially designed to work this way, and a VCS that can diff the binary AST in a syntax-agnostic manner.
This is what I'm currently working towards, as part of a programming language that is defined only by its semantics (the syntax itself is dynamic/extensible).
This will be deprecated as of PHP 7.4[0], and will cause a compile error in PHP 8.0.
However, instead of switching straight to right-associativity, PHP will require explicit parentheses to disambiguate nested ternaries.
[0] https://wiki.php.net/rfc/ternary_associativity