I have an idea for a process that might result in the discovery of an exploit in the JP version, but I don't know how to implement it.
Correct me if I'm wrong, but the fun started when Kadamony made the spreadsheet tool. Originally I think Keylie was going to make a run featuring the airship glitch. But it was the super-optimization of the sketch glitch that led to skipping even the Floating Continent and also getting Moogle Charms on everyone.
We've seen what the Goggles Glitch can do, and I think the Equip Anything glitch should lead to a big exploit at the start of the game. The Goggles themselves have a different effect in the JP version but there are still bad animations being played and bad sprites being drawn. The question is, what is going on?
I've tested every item from 5A-FE multiple times over the years but I've never known what to look for. The Goggles Glitch for example also requires specific timing. I could've been close to finding it and not known it. What if attacking with a TortoiseShld causes monster 5's common steal to change into a Charm Bangle? What if attacking with a Potion sets the Engulf bit for ally 4 only? If I'm testing against a Leafer then I'll never notice. I can't watch every known address at once.
But if a spreadsheet existed that listed each combination of (weapon id) : (list of addresses changed) then FF6 nerds everywhere could pick through the data and look for exploits. It would be a lot of data to look at, but we're good at it. And tests would need to be done. For example sketching the Intangir has always crashed the game with 100% reliability. But the spreadsheet led me to test one specific high-payoff possibility anyway, and the result was a miracle. Likewise some theoretically easy sketches actually softlocked the game. (Like so many outcomes involving the Moogle Charm, doh!)
I think this procedure might produce a good spreadsheet?
1) Play the game normally until Terra is alone in the cave.
2) Empty her hands. Get into a preemptive battle. Save state 'alpha'.
3) For each value 5A-FE:
-- poke it into Terra's L-Hand
-- save state 'beta'
-- attack, wait 10 whole seconds
-- stave state 'gamma'
-- binary diff 'beta' with 'gamma', and save all changes from 7E2000-7E3FFF
-- load state 'alpha'
Some variations in the initial state unfortunately probably matter: is the attack mirrored from the left side, what else might be in the R-hand, and potentially the position/size of the enemy. But at least to begin this should identify the dangerous items to attack with. I'd be shocked if there isn't at least one.
EDIT:
RAM map for reference. Check the theoretical spreadsheet against this, then look for exploits related to the description of that RAM address.