The first thing to make clear is that this is NOT a general purpose routable map, as it's specifically tuned for bicycling, and should not be used for automotive routing. (The best bicycle routes come when you tell this to use automotive routings.) Routing for faster time favours cycle tracks, while routing shorter distance takes you on cycle friendly (ish) roads if cycle specific options are out of the way. This carries over in other ways, in that a POI search for the "automotive service" will return nearby bike shops. Searching by address seems to work fine on my Dakota 20. Initial tests looks good, at least where the OSM data are good. But again, when I find problems with the OSM data, I can apply a fix, directly.
This encoding seems to be similar to that described by the Velomaps site, too. I've built OSM data using the Velomaps encoding (started before he started offering any options for North America), but that's slow and kludgy compared to getting this OpenFietsMap encoding, and in my limited testing, the OFM encoding seems to be working better.