Though I'm not a hacker, I'd agree the day is here. How well your hardware hack works would (I believe) depend on what output is expected. If an after-the-fact map/summary sheet
such as what Dan recently published with his claim is all that's expected, sure. But if it's to fake a batch of check-in emails and/or a live or delayed track, you'd still need to overcome a "secondary timestamp" issue.
Each automatically generated check-in email (from tracker company domain) has its own timestamp separate from the unit's (altered) timestamp. Similarly, pins on live/delayed maps would have to appear at reasonable times. You'd have to do this over a hundred times over the course of 1.5 months (based off #pings of other tracks: Anish=153, Dan=121 Stringbean~130, even Joey with trace unit has 100 out with 360 miles to go)...
It seems faking timely transparency is much more tedious. And based on simple math, the more thorough the documentation, the more chance of a slip. Per usual, the devil is in the details. This is why I continuously harp on the importance of getting info out sooner than later.