Short answer: NO.I'm gonna ask a stupid question. The fusee.bin in the atmosphere github page, what is the difference between that and the hekate_ctcaer_x.x.x.bin?
Previously i've been using the fusee.bin from Atmosphere and transferred into bootloader>payloads folder
while i renamed hekate_ctcaer_x.x.x.bin into reboot_payload.bin and place it in the Atmosphere root folder, and everything works fine.
For the current new fw, i've seen ppl use the modified fusee.bin by user Krejza9 as payload as well as renamed to reboot.payload.bin and worked.
So my question is by normal practice, is hekate_ctcaer_x.x.x.bin also a fusee.bin that i can just put into payloads folder as well as atmosphere root (reboot_payload.bin)?
Long answer: Don't hijack the thread. This is for sigpatches, not for CFW support. Fusee from the github page no longer can use sigpatches at all. You have to use sys-patch, build your own fusee.bin with ips patching added back in, or download the modified one from this thread (which has been uploaded/linked several times, so you better be sure you're getting the LATEST modified fusee). hekate is a bootloader that can chainload fusee.bin, or directly load package3, depending on your settings (hekate_ipl.ini).