I'm replying to myself lol, but for everyone else here it's also worth noting I took the boot0 from the pico and moved it to a hwfly system and did get the same error I was seeing on pico about BEK keys etc... But moving a hwfly boot0 over to pico didn't get me into HOS.
And before anyone asks, I tried fusee I tried from hekate... I tried injecting boot0 and trying to boot straight in, and also injecting then rebooting and trying again.
One thing I did notice and may be of important, when you first install the pico you will see the white led... This is either training Or some sort of initial diagnostic to check everything is working correctly or even the initial modification to boot0, the white led is either followed with a color to indicate a problem Or a blue led while it starting glitch timing.
Now when I flashed the hwfly boot0 and rebooted before attempting to launch in HOS I was greated with the white led again as if this was it's first boot, this makes me believe its coded to rewrite boot0 If the data/checksum whatever doesn't match its own code.
Im pretty confident that there is nothing we can do from a hekate/payload point to get this to "work", which I'm using very loosely because while I understand everyone is hyped and wants this to work NOW this isn't the correct way to go about this. As I have allready said and some others here have aswell, we need a completely open source firmware, this benefits everyone in the long run rather then some bodged up work around.
So can I ask, please stop sending me payloads etc to ask me to test, because I'm not going to bother at this point.. But I will still continue to test any UF2 firmwares for the pico itself.