1. Got it!
2. Oh, but I thought that using ChoiDuJour (not NX) was your recommended method for updating without burning fuses, as it can be done from the RCM without even booting into the OFW/CFW? Now I'm confused. What exactly should I do to update without burning any fuses AND preventing the cartridge slot from updating?
3. I know, I'm just trying to understand the difference between updating using ChoiDuJour (not NX) and using ChoiDuJourNX after loading SX OS and creating an EmuNAND. The second method looks easier.
4.1 Okay, so if I use Hekate as the payload/bootloader, I can boot into the OFW (which will be at whatever version I updated using Choi) without worrying about burning fuses?
4.2 Is it the same in SX OS, where it gives you two boot options? No need to worry about fuses?
4.3 I'm not planning on manually disabling AutoRCM or even going online (let alone updating online via OFW), my concern is AutoRCM being automatically disabled somehow and accidentally booting into the OFW without first going into RCM/using a bootloader, consequently burning fuses. Can that happen?
5.1 When you say "slower", do you mean in loading times? I don't mind the file size, because I have a 128GB card and will be playing mostly first-party titles, but I'd like to have the fastest loading times available.
5.2 I didn't even know you could use an HDD. Does it have to be connected to the Switch itself or can it be plugged into one of the dock's USB ports?
6. Understood! So NSPs are always available in the smallest possible size?
7. So they're performed alongside the firmware update even if I use Choi to do so? I want to keep my controllers up-to-date, since they have nothing to do with possible exploits.
8. Ah, so you don't have to choose between one or the other. It starts as FAT32-compatible only, and then you can patch to add support for exFAT, but still use FAT32 if you'd like?
And I did see your response to Charli. I added some comments to the list in parenthesis.
Thanks again for your patience!