I also wrote a custom MapResult data that allowed me to select one or more POI's or Ways in a returned database tile to only render parts on the tile so I could debug some issues in my rendering theme.
Additionally I wrote some helpers that for a given way or POI I could log what draw functions got called. It all made it much easier to debug and tweak my theme.
I am also working on a little tool that generates a report on the Map to Theme coverage, see what data is in the map file and not being used. It also gives a breakdown on the memory usage in the Map file, like how much memory is being used by strings or what ways (tags) are taking up the most space.
I have a project that I am attempting to fit the most maps possible in 2-3GB, so every MB counts, I also investigating a slightly modified version of the file format in order to optimise space, I don't need high performance just more maps!
Basically it lets me load a map and theme, when I select a tile I see that tile rendered using the elevate3 theme (on the right). I also get a list of WAY and POI, if i select 1 or more of these they are the only items rendered in 2nd map. The app also monitors the file system to reload the layers if I save my theme file.
When I started i knew very little about the OSM data so while it has helped with the theme design, it was more about educating myself on the OSM data and the Mapsforge API.