Sorry, I do have the latest Hekate on my SD card (mainly to create or migrate emuMMC, change AutoRMC, etc) then I just use the Fusee payload to boot into Atmosphere.
I have no Hekate patches in Atmosphere (although I don't see a problem having it), Hekate payload is only used if I ever want to go into non CFW sysMMC.
I'll check to see if the latest Hekate with patches still gives me problems with Tinfoil, since moving from Kosmos all my sysmodules work as intended.
Edit: Just checked booting with Hekate, Tinfoil sees it as Kosmos.
I really don't see a a point in booting with Hekate unless you really care about the 3 seconds it shaves of booting into Atmosphere.
Game (Doom 2016) loading times were the same for both. Tinfoil does not give you a message with Fusee and who know which files it changes in order to uninstall it's claim on Hetake offending files.
I never boot with Hetake anymore, it's more of utility for ease of SD setup there days than a payloader to boot into Atmosphere.
Even my Lanuch icon(s) in Hetake are configured to chainload Fusee emuMMC and Stock sysMMC (removed CFW sysMMC) but that's not the method I use to boot.
I have Fusee on my RCMLoader as the first payload and Hetake as my second payload if I ever want to boot into sysMMC or configure something in Hetake.
I’m kind of a noob, but I remember having to use Hekate to enable the game cart to work after updating. Is this not necessary with fusee?