Edit: this message was wrong. it was based on few information we had at that time. don't trust anything I said here.
*original post*
Based on what I've read and understood so far, there's no active redirection done by the kernel. this is not a real-time file redirection to another device, or even internal (it could have been internal redirection, but it's just easier to make two partitions and select the one to boot)
there are two different copy of your Horizon's partition content (system and files?) on your internal NAND. SX OS just edit the GPT partition table to change which partition to boot (it boots the second by default).
it's a dual boot, like if you have Windows and linux on the same HDD on your computer, you just choose the partition to boot. When you boot Linux, it's not Windows emulating linux, it's a real linux on a different location on the same internal hard drive.
SX OS reduces the current partition size (by moving all used sectors to specific location before resizing, it's probably this step which is slow and dangerous if you lose power), creates a new partition on the free space and makes a copy of your first partition on it. you just need to choose the partition you want to boot.
updating one, while not using SXOS will burn e-fuse, making the other unbootable.
The primary reason for this is that occupying 32GB of a MicroSD card is a bit wasteful. By default SX OS will allocate 15GB for your EmuNAND partition
apparently occupying 32GB on multi swappable big SD size is wasteful, but deleting 15GB of limited internal space is not.
So, I'd just like to know, if I play online on EmuNAND,
and if I get banned
Is my whole Switch banned?
Or I can change the thing that identify me as banned (Idr the name)
This will be the exact same copy of your NAND.
NAND 1 and NAND 2 are identical, they both share the same consoleID, user account and certs.
if you are banned on one NAND, the other will know it. you are banned server side, not console side.
You could probably, AFTER creating the NAND copy to the second partition, create a different user account on one of the two NANDs partition and then they will have different userID, but still the same consoleID and certificates.
Having your hacked NAND always offline will prevent nintendo knowing you hacked your console, letting you continue to use your untouched (one without cfw) NAND online.
The main idea of using any emuNAND is to keep the console's content clean, unedited, and for security reason only hack/edit/install homebrew on the copy of your NAND (incorrectly called emuNAND, should be called redirected eMMC, there's no emulation).
here, there's no "safe untouched NAND chipset" as your main eMMC's partitions are resized (therefore detectable), their content/sector edited which is very dangerous, and being counter productive to the safety reason of wanting to make a NAND copy !
