I see, how would that work out logistically? He is doing a segment when the RV passes. He gets picked up. He pauses the GPS. They drive him to Laughlin (35 miles). It's now 13:42 Eastern, 10:42 local time. The watch segment needs to run another 90 minutes or so, and he needs a decent amount of miles (less than 21.9, assuming he was picked up in the middle of his segment). He would need to make up miles...
This is interesting, probably nothing, since it only takes up about 10 minutes of their day, and they could have been scouting for gas or something. The tracker passes through Laughlin and into Arizona up Hwy 68 for the 13:30 check-in before heading back to the NV side, showing up south of their eventual hotel at 13:42, and then at 13:54 they are the hotel for their break. Tracker stayed on for 2 hours, until 15:33 Eastern, or 12:30 local time, just past the time RY should have ended his run. Pool photo is 12:52pm.
I'm not convinced. These are the "easiest" ways to get the distance and pace on the TomTom imo:
1) RY actually runs 21 10:00 pace miles unassisted through the Mohave desert on a 100 degree day
2) RY runs 21 miles on the road, and gets a short ride home (maybe even they give him a 15 mile boost, dropping him off outside Laughlin for the long downhill (where was that reference about the fast downhill into town?).
3) RY logs 1 minute miles in the RV, pauses before they get to Laughlin, and then lets the watch run
4) logging extra miles with the tracker at running pace during their break between 1 and 8pm