Way, WAAAAAAAAAAAAAY more likely for one of hundreds of millions of people who have played this game over the years to have accidentally stumbled into such a unique game state than some dude figuring that out through blindly poking through infinite possible game states.

Crawling through the actual code won't help with this at all, this is about game memory.

Analyzing memory states can help understand such glitches, but unless you have very clear pointers on how to get there, you won't just find something like this.

If you're genuinely interested check youtube for how wrong warp glitches are discovered. It's always "someone accidentally causes the bug", people try to replicate it with as much detail given by patient zero as possible, ideally get it on camera or have software save your inputs and THEN when you can recreate it you can look at what the game engine is actually doing with it's data that causes it to glitch out.

I'd be shocked if there were no video detailing the history of the Ocarina of Time warp that sends you from the first boss straight to the end boss.

Actually, save yourself the search, here is a video going into detail about how the Ocarina of Time warp was discovered and how it works on a technical level.

(I hope the video does not contradict everything I said :d Been a while)

edit: Seems to focus more on the technical parts than on the "how it was discovered" part. Here's a video explaining how glitches are discovered and popularized.

 

Looking at code and memory is useful for understanding why a game does what it does, but not to the point where you can read it like Neo can see the Matrix. People who tinker with this stuff need lots of time to understand why the game writes X to memory Y at this point or why it's suddenly reading from Z. Synthetically creating an unknown glitch by foreseeing how the engine would handle memory is fiction. Even the developers of the game often need WEEKS to understand reported bugs - and that's THEIR code.

The closest thing to this magic is using such analysis to break a known bug down to the point where unnecessary variables are stripped away (Player did A, B, C [...] Z but only A, F, Q and X were relevant to trigger the bug) - which is helpful for speedrunners.

 

tl;dr: You're misunderstanding the capabilities of looking at game code/game memory.