That's correct, the current implementation of VisualRF limits you to only monitored/managed devices, rogue devices, and active clients. I agree that it'd be useful to show neighbor, suspected neighbor, and neighbor clients, which makes it a good feature request to make through your currently open support case. I also agree that having colors to distinguish between rogues and suspected rogues would be another valuable feature request to make.
For now, you can potentially use the RAPIDS Export Threshold (under RAPIDS -> Setup). This is the setting that designates what data is passed from RAPIDS to VisualRF for display. It's a 'top and down' selection, meaning whichever option you choose, it and the items listed below it will be exported to VisualRF. If you set it to Rogues, you'll only see Rogues and Contained Rogues in VisualRF. It's set to 'suspected rogue' by default. Try to not set it to anything higher as that increases the number of items passed to VisualRF for location calculation. You want the data passed from RAPIDS to VisualRF to be of value instead of cluttered. VisualRF has a hardcoded limit to the number of RAPIDS generated items that can be displayed per floor which is done as a performance limiter since some environments can have a large number of rogues.
Also, make sure that your client is making use of the RAPIDS rules. It's important to classify as many heard devices as possible to narrow down the number of suspected rogues and rogues to a number that they will actually care about. I've seen many customers who have only the default rules which may not make sense in their environment. Things like coffee shop hotspots, video game consoles, teleconference devices, and scanners should be classified to something between valid and suspected neighbor.