Option 3 is not stupid - I’m building quarter inch breakouts, and those are easily used reversed. It’s mainly a headphones issue, being honest.
Of course, modifying that script means it will be overwritten on every update?
My instinct would be to somehow add something like an environment variable to flag the board as a DIY one pre-revision (reversed), which then branches code in the official script. I presume Supercollider can access environment variables, of course. But that would have minimal affect on everybody else, and be a change that persists over updates.
I appreciate this affects a small amount of the norns ecosystem, but right now it’s not insignificant imho, and it’s a feature of an officially released thing, hence trying to work out how to solve this with minimal alteration but in a relatively robust way.