The item that has been open through this whole run is answered: the paint order is the screen object's reordered child array at +0x30, not any table in the file. BACKLOG and INDEX now lead with that, and the investigation behind it is kept in full underneath — most of it refutations, which is what made the answer findable. What is left is stated in the same breath, because it is what the port needs: deriving that order from the bundle without running the game. Until then the viewer paints in declaration order and the title screen composites wrongly, which is now a documented defect rather than a mystery.