I've been making some custom maps for both Osmand and Comaps. The main big positive for Comaps I've seen is Android Auto being available freely (but you have osmand+ so moot point). But having used both, the tooling for osmand is far more mature. Creating an obf file (osmand file type) is a lot easier than the process for an mwm file (comaps file type). Far more routing or ui customization options in osmand and routing.xml files for even more advanced custom time penalties/weighting profiles.
The 100k figure is an overestimate by a few percent. The OpenStreetMap data for ALPRs is pretty good, but there is some duplication.
I (recently) programmatically identified ~2.5k such instances.
https://pickpj.github.io/Mapping/FIock/similar.html
It has openstreetmap links attached for those who want to help fix the data.
Consider balling up some electrical tape underneath the Ram stick. This solved this very specific issue with my laptop that was flexing too much and crashing.
Download osm data, extract roads and surveillance, gpd overlay how=difference, remove/edit the different osmid's, write to pbf file, convert to obf file w/ osmandmapcreator, import into OsmAnd.
Now you have turn by turn navigation around ALPRs on your phone.
To add, a bit complicated, but osm data can be edited with osmium (cpp) or pyosmium (python). Then the edited data can be put into osmandmapcreator to generate the file to use in Osmand. (I used this to route around ALPRs)