It could very well be the case.
Problem is that the writable volume (once created) isn't updated automatically when a new template is delivered. The only thing that happens is that new writable volumes are created with this template.
There is an update writeble volume option so you can update the WV's with the newly created snapvol.cfg (which is mostly the thing that changes). I really think that there should be some sort of change in applications to manage this better than it is managed now (just work with it and get the hang of it)
We are using a 2.6 template and still can work without issues.
I do agree with you though (regarding the other ticket between LWL and Appvolumes) that support and documentation could be a lot better. Also communication could be a lot better.
We worked with CloudVolumes before it was taken over by VMWare and to be honest support was better those days (oh how we love the old days) . Now it is often way to quit on the other end of the Ocean and my guess that a lot of stuff is actually happening, we just don't see it.
I would love to have some more interaction with the Appvolumes guys of the forum for brainstorming and stuff... So hopefully they read it and chip in on discussions.
For me though Appvolumes still is, hands down, one of the best products for our enviornment. We need dynamic composition because we have over 16000 users and only 1500 active sesisions. Regarding integration and the appstacks, it just works as intended. We still need to find applications that don't work due to Appvolumes. Mostly, if it doesn't work, it is a firewall problem or anything else. We do have all middleware installed in golden image (.Net Framework and VC Redists).