If it is the disputed distance for 28th Feb (Strava: 178.2; Garmin Connect: 215.8 miles) that has prompted this complaint, I can't see how this is a Strava problem. As far as I can see, the track is the same on both but it is simply the summary figure reported on Garmin Connect that is in error. The Strava data are the more reliable in this case. Unless there is some addition to the route that is not mapped on either service, in which case that sounds like a GPS/operator error, not one from Strava.
The point about Strava benefiting from the OYTT/HAMR publicity is undoubtedly true, but not a reason to change the rules part way through the event.
Talking of Strava, I see that Steve is down as winning the February MTS, 48.5km ahead of Kurt. Kurt's actual distance exceeded Steve in Feb (Kurt= 9139km; Steve = 8626km), but if I recall Kurt didn't join the MTS until part way though the month, so perhaps that's the reason. As a competitive rider, he may be kicking himself now for not joining earlier.