AT&T Wireless is the only carrier I don't have a phone to test.
I wouldn't put much stock in Anveo's advertising; "uncompressed audio" is simply the G.711u CODEC, which Google Voice (actually, Google Chat) uses, too. One issue that can cause these variations is that the ITSPs, including Google Voice, may use different intermediate or "transit" carriers on different calls. Their switches apply least-cost-routing and other variables to large tables of call routes. It's entirely possible for a call between the same two endpoints to take a different route from one call to the next.
We've also been having some recent problems with a few of the transit carriers dropping DTMF along the way. When Google gets reports of these instances, they have to nag the individual transit carrier to fix the issue, so it is a "whack-a-mole" process.
You can try making a bunch of calls to
http://www.testcall.com/222-1111.html to see if it always recognizes your end's DTMF.
If you can try Anveo (and/or other ITSPs) on a per-call pricing basis, vs. signing up for an annual plan, that would be worth experimenting. Ultimately, though, Contact ID is just not VoIP-friendly.