If you enable AutoRCM while upgrading your emuNAND with ChoiDuJourNX, autoRCM will NOT be activated on sysNAND but emuNAND, which is useless. It'll only work if you do it on sysNAND.
So that's what happened to me.
I installed the 6.2.0 update using ChoiDuJourNX after creating an emuNAND and had the scare of my life after the system rebooted into sysNAND/OFW/Horizon.
AutoRCM was definitely enabled in ChoiNX (as it is by default), but my heart sank when I saw the console booting normally instead of giving me a black screen (RCM).
Checked the system version: still 1.0.0. Rebooted into RCM, injected CTCaer-Hekate and checked the number of burned fuses: 1. Crisis averted.
Later, I enabled AutoRCM using SX OS's bootloader, so that should work from now on, right? And is there any way of disabling whatever form of AutoRCM was implemented in the emuNAND by ChoiDuJourNX, since it doesn't really work? I don't want conflicting software.
That doesn't make any sense.
You either use the dongle to boot into CFW or CFW emunand
You don't use the dongle to boot into OFW
If you use the dongle, then decide to boot into OFW you just press the OFW option.
You could use a dongle to inject a bootloader in order to boot into OFW without burning fuses, no?
Only starting the system normally (without booting into RCM first) would burn fuses - if the sysNAND's version doesn't match the fuse count, that is.