Thanks mate to pointed it out!To avoid a bit of confusion for others that reach this thread in the future, I feel it's important to point out that upgrading sysMMC either by official methods or via ChoiDujourNX, neither way actually burns any of fuses on the console...
BOOTING stock firmware is what burns the fuses. This is an important distinction, though it doesn't really seem like it at first. The reason being that while the N can determine the latest OS you should be on from update downloads, compared to what you are on, just by comparing their own logs, they don't (as far as anybody is aware) actually check for a fuse mismatch on the local console via the stock firmware at this point.
So, the big difference is that if you were to officially upgrade your stock sysMMC, but then ONLY continue to boot it via RCM with a mod chip or the like via the "stock" mode, you can have an "unmodified" system which matches exactly what Ninty expects you to be running from their remote logging. So long as you never boot Homebrew or load any CFW extensions, there shouldn't ever be anything unauthorized written to the debug logging to ever be reported.
Unless they release a new update to the consoles which actually does a local fuse comparison between what you have and what your firmware expects, and then reports that back to them instead of just using it to determine if you're bootable, and of course doing all that without the Atmosphere guys catching on and producing a new module which fakes the switch's fuse data to hide it when they support booting that updated version, you're effectively safe to run it as-is without burning fuses on your "stock" firmware.
To have fuses-UNburned will allow us to do a sysNAND downgrade, eventually?
Last edited by ThePirat,