@Hans-van-de-Ven-MRA-Master Your answer is besides the point I'm addressing.
When e.g. a standard member makes a route in OSM and you import it into your routes and you change the map set, the route will change. In order to have a reference you need the track for comparising. So before changing the map set, you need to save the track first and then import it again in your tracklogs folder before you can use it as an underlay in the mapset suitable for your gps. Even when one uses the same mapset you need the track before you can optimize the route (fastet to shortest and drag the route to the track). When you do this and send the route as a gpx1.1 (route, track, POI) to any one they will ride the same route for 99.99% (calculating algorithms in the gps differ from those in the route planner) after recalculation of the direct route in the gps (I hate track to route convertion in the gps as one loses the waypoints in the route and is only handy for large driving events where the route is split up in sections from stop to stop and one doesn't have to care about what gps is used).
Another advantage of recalculating routes in both fastest time and shorter distance is that a garmin user can leave the recalculation mode in the gps on 'on". Even the XT users I know whom uses MRA prefer this method i.s.o. using the gpx1.2
I have been using this same principle in basecamp for years now and even when I import an optimized BC route in MRA I still have to make changes just due to different calculating algorithms or small map set differences.