Having said that, a speed-at-distance rule like the one you give here, especially if it was evaluated at a distance before you expect to reach V1, would be perfectly good. There is a rule-of-thumb for small-plane pilots saying you should have reached 80% of the rotation speed before you are halfway down the runway (though that speed is also weight-dependent - as demonstrated in these incidents.) There is a tacit assumption here that your deceleration after choosing to abort will exceed your acceleration up to that point.
Basically, I'm saying the plane should have an internal mathematical model of what it expects to happen, and anytime that sufficiently differs from reality, it should trigger an abort - especially if you're still on the ground at the time!
It's often a judgement call when things don't happen quite right and I don't think our technology is anywhere near ready to hand the abort process over to the plane's programming.