I don't see anything obviously wrong, but I don't use Hekate or an emuMMC. I'd recommend booting into your emuMMC using fusee-primary to help figure out where the problem lies. If the games still refuse to work, you know the problem is unrelated to Hekate and its settings. If the games work, then you know the problem is related to Hekate and its settings.
Also, are you using the latest version of Hekate?
My guess is it checks for an emuMMC in the conventional spots. If it exists, it loads it. If it doesn't, it doesn't.I want to ask you a question, how does Fusee know to boot to cfw EmuNand and not into Cfw sysnand? I remember when I started out, it boots direct into cfw sysnand and I don't want that to happen.
I see, because only booting with fusee I am able to install some nsp games that wouldn't install when booting into the cfw emunand with heckate.My guess is it checks for an emuMMC in the conventional spots. If it exists, it loads it. If it doesn't, it doesn't.
You can check if you are in your emuMMC by checking the version string in the system settings.I see, because only booting with fusee I am able to install some nsp games that wouldn't install when booting into the cfw emunand with heckate.
To add on, there will be a letter E signifying you are in emuMMC.I see, because only booting with fusee I am able to install some nsp games that wouldn't install when booting into the cfw emunand with heckate.