Hi! I think I can replicate your problem.
Since you posted your query, vscherb gave some more info on github about the file naming scheme for OSM Live incremental updates:
Typically patches are called and sorted (the last one is the most important patch):
Map.obf (full)
Map_19_09_00.obf (patch for 09 month overrides full map)
Map_19_09_13.obf (patch for 09-13 day overrides 09 month patch)
so I thought I'd have a play. My method was to use JOSM to download a single node or way, edit tags, and save as .osm; then use OsmAndMapCreator to create .obf from the .osm file.
First I verified that naming the result zzz.obf would cause it to update the main map by changing a way that is part of a trunk road to be a bridleway. This worked and was easily visible on the map.Then, instead of changing to bridleway, I added access=no to the way. This made no visible change to the map, and OsmAnd happily routed cars through it (I had checked that "Allow private access" was turned off in the navigation settings.) Same thing if I only add access=no to a single node of the way.
For the case where I added access=no to the way, I checked with "inspector.bat -vmap -vmapobjects -osm zzz.obf" and the access=no tag was confirmed present in the .obf
I'm just a curious user, so unless I think of something else to try, this is as far as I go! And I don't guarantee that I didn't make a mistake. But I hope this is some use.
Good luck!
OsmAnd+ 3.4.8 (Android 9)
OsmAndMapCreator 1.8 (windows 9.1)