if you want emunand then use it. why are people here so against someone using it?
Because in most cases, it's not as needed as it once was and ends up complicating things (have to keep sysnand at a low FW etc)/takes up space, have to keep track of the correct nand dumps else you could end up bricking if you restore the wrong one etc.
I can understand the requirement of an emunand back in the days of RXtools etc where homebrew was dodgy and there was no telling what Nintendo would do next (patching entry points like Menuhax), so it acted like a safety net but since A9LH is so deeply ingrained in the 3DS compared to other CFW methods (like menuhax) - if something goes wrong, you can easily undo it.
Unlike Homebrew exploits like Menuhax, A9LH is not a simple "patch a few holes here and there" affair to get rid of - which links back to the whole "not as needed as it once was".
Then comes the issue of accidental system updates to your Sysnand, which could end up breaking A9LH completely (preventing it from even loading payloads) where it's still possible if you run with an updated sysnand approach. Now, of course A9LH has changed a lot since I initially installed it and this may not be an issue anymore, but it was when I first installed it.
Finally, it's your 3DS. If you want an Emunand, sure - go for it but there's still better options out there. Just because "it just works" doesn't mean it's the
best approach for the long term (on that note - it's the same story for RXtools users who've been forced to update to a newer CFW to be able to play Sun/Moon).
