It's surprising that no one has thought it up yet. DKC2 is most likely storing executable code in SRAM where it always expects it to be in proper condition, but the glitch (as it causes arbitrary code execution from a location which is not code, due to the fact that it jumps to pointer no longer functioning) could possibly corrupt the code in the SRAM.
Because the SRAM code is now corrupt and it's (possibly) run at the game's startup routine (initialization for something?) it causes weird behavior to happen. That is why the damage is sometimes thought to also expand to the ROM image / cartridge.
I'll test this theory at some point. Any volunteers? Try to get this glitch happening on an emulator or the real SNES. Emulator is better since you could debug if the game stores code to SRAM to begin with.
When the glitch happens, remove the .srm file if using emulator or remove and re-insert the battery if using the real SNES. See if the game suddenly starts working again.
Because the SRAM code is now corrupt and it's (possibly) run at the game's startup routine (initialization for something?) it causes weird behavior to happen. That is why the damage is sometimes thought to also expand to the ROM image / cartridge.
I'll test this theory at some point. Any volunteers? Try to get this glitch happening on an emulator or the real SNES. Emulator is better since you could debug if the game stores code to SRAM to begin with.
When the glitch happens, remove the .srm file if using emulator or remove and re-insert the battery if using the real SNES. See if the game suddenly starts working again.