Determining the uselessness of a section of data in a game is ever the tricky thing.
If your emulator has a trace logger ( http://fceux.com/web/help/TraceLogger.html
, and I am told no$gba might have just got one too) then you can run that and have it note if some piece of code/memory is executed/read. Can do well if you do all the actions (including any idling type things, options menus, cancelling out of things, credits, cutscenes... in an ideal world) but there is the option for some random bit of gameplay to go to it. A more basic break on read/execute or log equivalents thereof will also do something but the full trace logger might give you a better idea of what is executed around it and thus whether it is likely to be hit up at some point.
You can run a disassembly over it and try to see if anything calls it/references it. Sometimes you find something (or indeed nothing) but that does not take into account any pointer maths most of the time. I have not pulled apart enough SNES games to know how much it does with any pointer maths, though on later systems it is not uncommon at all. You also tend not to get as many surprises on older systems where it tends to run through set patterns in code (think levels 1 to
where newer ones can ping around between minigames, maps, menus and more all within the same scene. Games are games though rather than straight shot find and replace and write out and exit data conversion programs so always the option for it.
I don't know what the binary encoding of that will be offhand but not all data within a ROM is code -- if that happened to be a nice blank tile you just overwrote...
Runs of actual instructions do have their uses in coding, though probably not here (no point in doing a NOP slide in a SNES game as the original dev and most things don't need that much waiting*).
*if you think you might have a race condition, or are waiting on a slow bus, then you can code it properly with nice indicators and interrupts or, especially if every cycle counts is your mantra, you can add in a bunch of thumb twiddling instructions so you can be reasonably sure you are past the danger zone.
For super mario kart it did seem that the source code was leaked. That might also offer some insights, or might not and comes with the downsides of being leaked code. Might however have some labels and comments that make things have some context.https://datacrystal.romhacking.net/wiki/Super_Mario_Kart:ROM_map
might not be complete but has some data on what goes where, and I am sure whatever passes for the SNES Mario Kart hacking community will have a bit more still.
For the most part if it looks good and a few of the sanity checks above did not reveal anything then give it a go and check that as well. Hard drive space is cheap and ctrl and z works too. Maybe you get to come back in a few years as someone discovers oh no it actually did something after all, or not.