OpenStreetMap policy is to split a road if there's a barrier between the sides; it captures the fact that it's physically impossible to move to the other side of the road. In this case, Torbram is "properly" split in the sections where there's a median.

I believe this routing issue is caused by OSMAnd not being smart enough to recognize the transition between the split and unified sections of road, and so it interprets the U-Turn from the Northbound split section to the Southbound one as being a left turn in 3-way intersection, which is presumably much less "expensive" in the routing algorithm than a U-Turn.

If I'm right about that, then the "correct" solution is either to mark these "left turns" as explicitly banned on the map, or to make OSMAnd smarter about interpreting the existing map; I don't know which. I'll ask on the OSM wiki talk pages and the OSMAnd issue tracker.

Incidentally, I agree that duplicating intersections is a very dumb consequence of split roads, which is why I've started merging roads on the very short segments that are actually inside the paved intersection area. It's even consistent with the policy: there's no barrier on /that/ part of the road 😏.