Hekate is not a CFW, it is a bootloader aka the tool used to run CFW like Atmosphere, ReiNX, or SX OS.
The issue with firmware 6.2 in a nutshell is that in order to patch the firmware, it needs to be decrypted. These keys were all kept in the bootloader which we had full access to. Now one of the keys is in another chip outside of the bootloader known as the TSEC and we can't access the TSEC without a TSEC exploit. This will be a problem for CFW and piracy down the road if not cracked once games are encrypted with this key because we can't dump anything that uses it.
I see, so then the issue with not getting my 6.1 keys before I update to 6.2 would be that I would not be able to downgrade to 6.1 (though since that would lock me out of any 6.2 or later games, that would still be it's own issue) and not be able to install any CFW at all until someone manages... if they manage... to find a TSEC exploit?
From what I understand though with how the efuse thing works, the official firmware is coded to make sure a certain set of efuses are not blown, and if the number blown is larger than the number not blown it will refuse to boot, right? I always assumed it was something in the CPU itself doing the check somehow, so if it's purely in the software, would someone be able to remove that check somehow in a CFW? Or are we not able to decrypt and re-encrypt/compile that part of the firmware that has the efuse check?
And if a TSEC exploit is found, does that mean there would have been any benefit to backing up my 6.1 keys if I had waited to hack my Switch until then?