Can I ask why that's the case? If it's a brick risk that applies to any CIA installation on SysNAND. Not everybody wants to bother with setting up an EmuNAND and if something behaves properly on EmuNAND shouldn't it function on SysNAND, not the other way around? It seems like isolating an entire subset of users simply for the sake of "eh, don' feel like debugging it".Support for sysnand has been dropped. You have to run them in emunand.
I know you're not a dev but you follow the thread closely. Did they ever specify as reason as to why?