Well my idea has probably already been tried by all the experts. Seems to me that what we need is to find the line of code responsible for counting the number of events and alter it so it's convinced the number of events is always zero, thus negating the problem. Now 'cause I'm a total newb at this I'm probably talking a load of bollocks, but if we have these emulator programs that allow us to find the part of the code that triggers the errors when they occur, logically the plan should be to deliberatly trigger the 24 event freeze so the area of code is identified and edit said code from there. But I'm sure if it was that simple someone would have done it and fixed it by now. I assume the problem is that I've misunderstood and the code isn't so easy to find. But that seems to me the logical area to focus on. Either that or just enhancing the Stealth Mode on most cards these days so the game doesn't know it's been stolen, which is probably best left to Team Cyclops, etc.
EDIT: whoa, typo army. Sorry about that...