Undesirable behavior writing to em_rsiz.dtt_rsz with exported json changes

[iSharingan]

Saving changes to crown size tables as a json creates one summary instruction "Crown_Sizes": {} with changes combined across all edited tables. When the json is loaded, it applies the changes to ALL of the tables, which somehow causes large monsters in Iceborne cutscenes (base World cutscenes are unaffected) to be misaligned (I can't seem to narrow down the exact bytes affected, but it might be in one of the "Spare Frame" tables that separate the proper tables). This won't crash the game, but it can cause monsters/corpses to fall outside the map and get stuck on the roof of lower areas (IE: in the Rotten Veil). If they fully zone out, they're placed back on the map, but in cases where they get stuck on a roof, pathing often breaks and it forces the hunt to be abandoned/restarted so the cutscene won't play (or in the case of corpses, they become inaccessible).

Edit: I refined the candidates for this behavior and ruled out overflow writes as the cause, in case anyone else has the same issue when editing monster size tables. The possibilities appear to be limited to the "Spare Frame" tables (no letter and colon before it) on all sizes but 100, "B:" and 'D:" crown table sizes over 120 (120 is safe, 121+ may not be), "C:" series tables over size 122 and under size 97, and possibly "Default Size Only" on any size but 100. Avoiding those 'taboo' entries will prevent the cutscene issue from occurring.

[Synthlight]

This is an issue for any struct that has sub-structs, so it also affects mkex as another example.
It also breaks for files that have strings in them but no-one ever does that so it's never come up.

It was just never designed for stupid complex files like that so got ignored. I might change this if I ever re-implement it for the MHR editor and backport it, but consider it minor for now.