Just to be clear, it’s impossible to downgrade a Switch with a hardmod. It had an array of eFuses inside the processor chip. Think of them like a bunch of tally marks. Each major firmware update blows an efuse, or marks a mark. If you downgrade it’s eMMC via hardmod, its efuse count will no longer match the version count, which means it will refuse. But worse: it will also blow yet another efuse to mark it as having been tampered with.
There may be, and in fact probably are, ways to hack it unrelated to downgrading. But downgrading is not an option. Every time Nintendo patches a “STAY ON THIS VERSION!” vuln it’d be silly to expect that patch to not also blow an efuse.
Me? My switch is running 3.0.1. When that version no longer works online maybe I’ll upgrade it. I didn’t realize that there was a confirmed vulnerability which was confirmed patched in 3.0.1 until after I’d already updated. At this point, unless I hear something concrete about 3.0.2 patching another exploitable vulnerability which is developed for, I have no reason to stay on 3.0.1. But chances are, if I upgrade, there’s no going back.
Edit: oh wow, what page am I reading