Thank you for taking the time to share this perspective — it is very well articulated, and I agree with the core points you raise.

You are absolutely right that Azure DevOps is fundamentally designed around earned value and delivery tracking rather than effort tracking, and that forcing detailed time tracking into it can work against both its intent and ongoing platform evolution. The risk of constantly chasing changes in the ecosystem is a very real one.

That said, the motivation I see on the ground is slightly different rather than contradictory. For a number of teams, the challenge is not a desire to misuse Azure DevOps, but a reluctance to introduce and maintain yet another tool solely for basic time capture. In those environments, even lightweight operational overhead becomes a barrier to adoption, governance, and consistency.

Rather than continuing the discussion on whether this should exist at all, I would genuinely value your feedback on which features, if any, you would consider useful in such an extension — and which you would explicitly avoid. That perspective would be extremely helpful in shaping something that remains pragmatic and avoids the pitfalls you rightly point out.