The change in #16578, although necessary, was over-sweeping.
I was initially in favor of it, but never expected this. It is turning into a boondoggle, with repercussions from our testing process (#17013) to MacOS user experience (#17025, #17179). Even changes outside the GUI code itself (#17184). I feel this is getting out of hand. It creates a lot of work and we'll end up reverting all of this eventually.
Perhaps there won't be more surprises? Otherwise I agree, we could revert and then blacklist some arguments instead.
There is not even a need to blacklist any arguments.
I mean, it's only a potential problem for one specific OS, in one specific use of the executable. MacOS shouldn't even have to be affected by this.
In any case we're not going to add custom Objective C code for argument parsing on MacOS or something to work around this, that would be total madness.
Considering #16578 (comment) is this still an issue?