well it seems with no cool exploits likely to come out ever, the work that goes into keeping them intact just doesnt seem worth the effort i guess.That depends, have you used CFW/homebrew? If you have, then you will have to keep using CFW/homebrew to update the firmware. If not, then do you want to prevent your fuses from being burnt or not? If the answer is yes, then there are a few more options that involve varying usages of CFW/homebrew. If you don't care, then you could just update it online like normal.
The best way to answer the question is actually the opposite: is there a point to burning the fuses? If you don't have a hacked console, you don't have a choice but if you do, then you have to weigh the risks versus benefits. There are many benefits which includes the ability to load lower firmware versions without hacks which in turn can lead to utilization of a future exploit. The only risk however is that Nintendo might notice there aren't a proper number of fuses burnt and drop the ban hammer. But in all of the years since Switch hacking became public, no ban has ever occurred solely due to a mismatch in the fuse count. Therefore, there is no inherent risk in keeping the fuses from being burnt but instead there are potential benefits.
anyways, other question, an emunand setup where you want sysnand to stay clean, if you use sysnand/atmosphere, should i only use homebrew via album, or is loading homebrew via a game tile still preferred?
Last edited by Clydefrosch,