Unless you're a dev, what purpose do you even have to use an emuNAND?
I can understand installing it to test your method if you're paranoid about installing to the system, but seriously, what's the difference between emunand and sysnand to a NORMAL user? I personally do have an emunand but I also play with things that could destroy things.
But for normal users who just wanna "backup" games, play with some homebrew now and then, there absolutely is no point that I can actually think of.
"To protect from a brick" that falls under "play with things that could destroy things" before anyone tries that argument.
I'm not hating emunands,I do use an emu because of my FW I play around with, I just dislike seeing normal people defending something they have no true use for, it's idiotic.
Also A9LH is a better choice for "normal" users, it takes less space, payloads boot prior to console booting into it's OS, and because of this method, the sysNAND can almost always be restored.
The only time is can't is if you're personally playing with things you shouldn't as a normal user and that falls back under why devs use emunands.
So being a normal user, installing themes, cia files, etc. You have no issue, worst case I ever had with a bad cia file was it freezing when trying to load it.
tl;dr
dev = emunands, because playing with code that can destroy things permenently (Never had that issue though)
user = A9LH, just use backups and homebrew, occasional cia install, 100% easy recovery
