Osmand makes an insane d-tour when destination of a "via" secondary target is on the other side of the highway

Describe the idea

Hello Osmand, I'm not sure if it is just me, but I still use waypoints and secondary "stops" to force osmand to use a certain route navigation. Gernally I just use such waypoints when travelling larger routes so all my seconary "stops" or waypoints I use are generally somewhere on a highway. By definition each direction of a highway is a one-way direction.

Assume now I want to travel north, but the "via" waypoint is on the south side of the highway. if you will the "wrong" side. While technically correct, osmand essentially wants to make perfectly sure that the "seconary stop" / "via waypoint" is passed. So it will exit the highway, turn around pass the checkpoint on the "wrong side", exit again and then continue the route in the right direction.

Expected behaviour

Again osmand might be technically correct, so I feel this is no bug, but more like a feature request to ask osmand to have an option in osman that it is fine to use a secondary target as waypoint (e.g. it is fine to pass close-by on the other side of the highway), instead of forcing a "I must pass this waypoint under all conditions".

Consider for example: https://osmand.net/map/navigate/?start=52.159210,12.780323&end=52.097549,12.688873&via=52.127945,12.747094&profile=car#15/52.1196/12.7362

Expected route: https://osmand.net/map/navigate/?start=52.159210,12.780323&end=52.097549,12.688873&profile=car#13/52.1052/12.7705

Alternatives you've considered

Once the waypoint is passed, remove it from navigation (somewhat annoying when travelling on a high speed road).

Context

Device : RE513CL1
Brand : realme
Manufacturer : realme
Model : RMX3241
Product : RMX3241EEA
Build : RMX3241_11_F.11
Version : 13
App Version : OsmAnd+
Apk Version : 4.8.6 4806

osmandapp / OsmAnd