FF6AE

I can see some advantage to use a pointer table for reordering purpose of an event editor. If your event at CB/7900 once packed free up 10 bytes after its FE, you just go through all the table and you do if pointer > CB/7900; pointer -= 0x0A.  You still have to do the same with all B2, B6, C0-CF commands concerned but it's a step in the right direction if I understand correctly. This example concern only code packing / optimization which is not a mandatory thing. I think an event editor should disallow expanding events directly in $CA-$CC if the editor does not perform optimization in those banks because of the little free space in ending of $CC, some of it being used by FF3usME and patches.

Also a pointer table could allow an event to land directly in expanded ROM (or other ROM free space), removing the need of a B2 call in $CA-$CC.

You make good points there. Being able to re-order events could lead to byte savings with the $Cx commands in particular, and patches or hacks could benefit from having related events close together. This is not to say that it would be really any easier mathematically because of the way events can call one another or branch into one another, but my point is that event $3125 would stay event $3125 no matter its address, and whatever event extraction/insertion tool that is created would, just like an assembler, be able to tokenize the events by number and fix the references.

Medium-term needs, I'd suggest clearing any non-event bytes out of $CC-$CD, which the original code can handle no problem. A long-term, even more massive overhaul would require changing how the event loading commands themselves work in order to subsume more than 4 banks, which would then have no reason to stay in their current location anyway.