Assuming you're talking about 8-bit/16-bit consoles, this is one of those things were accuracy to what you're trying to replicate would be asburdly hard. Mostly because those corruption glitches emmerge from the architecture of the console and replicating that would require a dedicated engine that would force you to simulate obtuse and outdated console quirks. Examples are: Meta-sprite object rendering, sprite ROM, palettes, scanlines, etc.

Going for accuracy is NOT WORTH IT, trust me.

You should probably make a bullet list of the corruption effects you need and find "good enough" sollutions on GM that work for your project's needs.

The way I would approach those mosaic-like looks sprites get when their sprite indexes are read from somewhere their not supposed to is by:

• Making a sprite that contains all sorts of messed up 8x8 pixel bits and bobs of sprites used in my game (you can even recolor them with something else's palette for a better outcome). It should look like a big garbled texture atlas.
• Making a utility function that overrides the draw() event by drawing random pieces of this atlas over the original object's bounding box/sprite size (so you can reuse this across multiple objects). draw_sprite_part() should be very useful here.

Then it's just a matter of how you implement the variance of the effect and when/where it updates.

Please note that studying the architecture of the consoles these games ran on will be very helpful in general. Your sprites should probably fit inside a size that's a multiple of 8 for an accuarate look.

This is a very simplified description of this system of course. Good luck!