I have no dog in this fight, but that Fort Worth marathon upload looks quite sketchy and makes me think the file was tampered with:
1) Watches "acting weird" don't get elapsed time wrong. GPS tracking may be off, moving time may be incorrect if the GPS thinks you've stopped leading to skewed mile pacing, whatever. But the most basic function of a stopwatch is to get elapsed time correct. Total time on this activity is 3:06:32, his official result shows 3:08:24 gun/3:08:16 chip. His GPS starting and ending points are exactly the same spot, so it's not like he started the watch late or stopped it early.
2) A typical activity when viewed on Strava (desktop) will show what kind of device recorded it. Many of Dane's recent runs are recorded via iPhone, in others such as the Ely marathon he uses a Timex Ironman GPS watch. This activity does not show which device was used to record, which means that Strava wasn't able to tell based on the file uploaded
3) Others uploading the same race consistently report a 6:59AM start, as do the official results, but this shows noon. In a modern watch there's no way you can have an accurate GPS signal but an incorrect time - GPS only functions by computing time differences from the satellites, without time there is no location tracking. Noon is an especially fishy incorrect time, since many software systems set this as a default time. For example, if the file was uploaded manually to Strava and the time information couldn't be read out of it, they may likely default the time to 12:00 PM.