Ultimately I think AUK will need its own repository for GPX tracks (and a means to create them). A reliance on third-parties like RWGPS or Strava, always carries the risk of the relevant useful features being "improved" out of existence, or hidden behind a paywall.
Personally I don't particularly like RWGPS, I don't use it often enough to remember where every thing is in a rather complicated UI, and I'd rather create my own from the routesheet to get a mental picture of where the route goes anyway.
The problem with a means to create them is unless you throw serious money at development you're just going to pick up an existing mapping provider's routing API.
And that has costs of its own and may also result in the features needed being "improved" out of existence.
Though in the case of google I'd safely say that every thing they do makes their software worse, some day they're likely to improve themselves out of existence.
The power of RWGPS comes from it's complexity, the simplicity in Strava and Komoot seems to result in that they just take you where everyone else goes.
And on that final point, isn't that what everyone should be doing as part of ride prep regardless of what navigation method they use?
GPS routing often has a few oddities that the route creator hasn't spotted...
Like the time I routed myself through a pub car park laid with deep chuckies, it was the only routing algorithm oddity I didn't spot, I'd cleaned up 15 or so.
Oh and this time:
Interestingly, the only time I gave way to the gps users on the Easter Arrow, we ended up going the long the way round. Not that I'm bitter...
You were pretty adamant on the junction that we were trying to turn the wrong way, and you were right.
We should have spotted when checking the GPS files over that it went wide of that control by a fair distance.