Okay, that's way more detailed than what I'd come up with.

So, with the player's data ending around 0x58, and with the Hijack data beginning around 0x6e, maybe for now we can just block off the 16 bytes before the Hijack data (0x5e-0x6d) for user apps?