For the SC issue: I've had that happen the odd time with someones softmod. I just end up having to delete their profile. If they're getting a softmod, they won't be going on live anymore anyways so it's not a biggie.
For trying to run it: Before everyone just figures they are going to run this gamesave and be in, I think everyone needs to read up and learn how these exploits worked. I'm no expert on it but from what I've READ and not guessed, basically the game save lets them trigger a buffer overflow which lets them overwrite the key in memory with something easily divisible by 3. This then lets us resign the xbe we are trying to run with a key that can be calculated easily. This probally won't work since they have probally changed their public key and as eveyone says, the hypervisor will catch any buffer overflow. If you don't believe the hypervisor will do that, READ the pages and pages of info on it. That's the whole purpose of the thing. In some cases this XBE was Evox. Sometimes it was PBL or NTPacker. PBL and NTPacker are going to be useless because they load a patched bios or patch the current bios, both which are XBox bioses and not 360 bioses. Trying to patch the current bios which we know nothing about, will do nothing but get the hypervisor mad again. As for running the game save that just loads the resigned evox, even if it did run or something, we'd only be able to see the XBox1 partition at the most. It's not coded to see the 360 partitions since it's a different file type.
We're only talking about an emulator here and not the actual system. Try using one of those VMWare products for a while and you'll appreciate whats going on. It will let you boot up a whole different instance of your computer and operating system in a window, you see the bios booting up again and everything. The nifty thing about it is that you tell it what resources it can see and can't see, and if that instance of the operating system crashes, it only crashes that window and that instance, not your whole machine.