Reducing dash/dasm/dast/whl1/whl2/whl3 vertically would, however, make the file quite a bit smaller, now that we (kind of) know how to set mystery bytes. BTW, there is another catch: ins(m)1/3 coordinates are relative to ins2 - they do not appear at all on your original dashboard because Y=147+166 is well below the screen. Setting their Y to zero on your original file causes them to interfere with ins2 and trigger the graphical corruption instantly when the game is paused. That should be accounted when restoring your original inm/ins and setting the definitive unknown values.
Another speculation: I wonder if dasm might act on dash as well as dast - probably not, but worth trying maybe...
