HyperV with RemoteFX GPU is probably the most common deployment with vWorkspace. Hyper V is much more cost effective than other platforms as you can just add a RemoteFX compatible GPU and then add a shared RemoteFX graphics adapter to all the VDIs that you want to benefit from hardware acceleration. However the trade off is that a lot of CAD or design products do not yet support the "RemoteFX shared GPU" for hardware acceleration.
This all expected to run over the LAN, if you want to run over the WAN you may run into performance issues (depending on bandwidth available).
It also really depends on the software that the end user wants to run, as RemoteFX (softGPU) on RDP 8 enabled remote machines I.e. Windows 8 and server 2012 R2 can run things like AutoCAD (Autodesk) very well.
However for video playback a GPU may not always be advantageous, as only some media players can utilise a GPU but be aware that although the rendering may improve you still have to transmit that data / video back to the end point, so latency / bandwidth is more important than the GPU inside the VDI. Check the properties of example video files in Explorer or VLC for file size, bit rate, frame rate etc. These numbers are important for calculating how much bandwidth you need. I.e. averages of videos, how many users will be playing video at the same time, average bandwidth consumption normally etc
There isn't RemoteFX GPU for RDSH at this time and therefore you won't see the same level of density using VDI over RDSH. However using full desktops in a 1 to 1 relationship brings other advantages.
Finally, as mentioned even just leveraging the RDP 8 protocol (with UDP transport) you can see big improvements in Windows 7 (and 8) VDI so that would be worth testing and could be set up quite easily.