I know why, actually. Because fusee explicitly derives all masker keys and always uses the latest available master key regardless of firmware. Because exosphere supports just using latest master key regardless of firmware, so you end up being able to run software encrypted with the latest master keys even if the firmware you're running doesn't natively include them
https://github.com/Atmosphere-NX/At...06befa2d3957ef74a37120f3f39749b5f12d5d5213028
This comment that I remember seeing before sheds some light on this
https://github.com/Atmosphere-NX/At...8e6c6a549ca894278f6fac0cd1e6d66235e3705e1cL85
Hekate doesn't do this, instead it does it more "cleanly" (read: more faithful to official nintendo bootloader) by only loading what is officially supported by that firmware version. I guess scires was just lazy and took shortcuts in programming, because it's so much easier and less complicated programming to just hardcode in the latest master key sources and guarantee all firmware versions will work, than to make it check firmware version and derive master key based on firmware version (the code in hekate gets pretty complicated here, where fusee just says "here's the latest master key, enjoy")
I withdraw my objections and my apologies to
@guily6669 for the pushback. I had a bias against you because of other stuff I saw from you in the past and just assumed you were wrong, without taking the time to check anything. That's on me
That being said I don't recommend relying on this, because it will only get you so far. You might be able to run games that want higher master key, but there will be a point where games will just fail to work and it won't be clear why. You can't spoof sdk version, if a game was built for a newer sdk version and uses functions only present in newer firmware, it will appear to install and run fine, and it will verify fine for corrupted data, but it will malfunction and likely crash during gameplay without really anything to indicate why (while if you run through hekate, installers won't be able to install anything
too new because of master keys, so you can just rely on that to know if it installs = it will work)
Also I wouldnt make an issue on hekate repo, there is no bug and everything is working as it should. Fusee just takes shortcuts while hekate took the time to do it "correctly", to "fix" this would require scrapping all that code in hekate and replacing it with what is essentially a hack, and that's just not going to happen