Save states can crash randomly. It's rare, so it's unlikely to happen twice in a row, but it can happen. That doesn't mean the save state is broken, and won't (eventually) work.
And I can't reproduce that that interp/jit issue.
You tried the interp/jit issue on XBC? Out of the 25 games I have dumped, that one was the only that exhibited such behavior. Certain save states produce the error "Program tried to read an opcode from [00000000]. It has crashed." each time I try to load them. I can post that save state if you're interested.
I'm still certain that I've encountered broken save states twice in the past (that is, loading it again caused it to crash regardless of what I did) on 4.0, which again is why I overwrote them (using quick slots of course). Since I'm picking up XBC in Dolphin again, I'll let you know if I come across anymore (and make sure to preserve them this time).
Yes, i did. It worked fine.
I don't know what else to tell you, it consistently fails on my end. I'll put up a couple of save states tomorrow when Google Drive stops fighting me.