Nice! Missed this one. But about data: still we could have a diversification about read and read-written?
The usage stats actually do track reads and writes separately, it's only the memory viewer that (currently) uses the same color for both.
On a related note, I was recently discussing reworking the usage tracking, including adding more specific usage contexts (see this github issue
for specifics). It'll most likely be an upstream change in bsnes-classic whenever that happens, but aside from that, I've also considered adding a way to customize the colors (including separate read/write colors if it'd be useful).
As for labels, I did plan to add support for those later on as well (probably similar to the way they are handled by the FCEUX debugger).
The debug does not show the address to the FX-BUS?
Right now, the SuperFX debugger only shows all the registers that are relevant to the current and previous instructions. I did this before writing the actual register editor, which makes it slightly redundant, and I might reduce it to showing the current instruction's registers to make room for other relevant info (like ROM/RAM access locations, such as in your example).