Accepted Solutions
While you are right that by using a floating pool, you kind of remove the value of the User Personalization Layer, you still gain a lot of advantages.
1. You still get to keep exactly 1 gold image of the OS.
2. You still deploy the apps as layers.
3. You still get the storage savings.
I would even add a fourth: the machines go back to default when the users disconnect. In any floating type pool, you are going to have some sort of roaming data solution in place. Maybe roaming profiles and folder redirection from a strictly MS background, or a third party solution of some sort, whatever, so there's no loss of features as far as the users are concerned. As someone who has 15 years of dealing with those from a terminal services and desktop support model, let me tell you that I would've loved nothing more than a system that would automatically revert to original state with each reboot. 
I have a floating pool built on "Unidesk VMs" that I use for remote access purposes for everyone and for our standard users in the office. I have all the base applications that we use loaded in it. I use folder redirection to send the Desktop, Documents, Favorites, and Downloads over to our storage system, then have MS roaming profiles configured for an OU containing these machines. Appdata basically is all that gets stored on the profile share, so user logons are super quick. I've even turned on Microsoft UE-V, which is so slick I just giggle every time I see it work (basically saves application configs in a central repository as XML files and pulls/pushes them back when apps are opened, closed, etc.) UE-V allows my full PC users to have their applications settings, such as their Office Themes or whatever, populate into the VDI environment automatically, giving a more consistent experience across devices.
Anyway, don't throw it all out just because you won't get the user personalization layer on floating pools. There's still a ton of advantages with it....
You have to keep these things in mind. Any applications pushed via GPO, SCCM, WSUS, or any other management application will get dropped into the User Personalization Layer. This is one area that I could see being an issue. If you then go back and run updates on the base OS or on an application layer underneath, and update the machine, the user personalization layer changes will still take precedent.
In our environment, I disabled Windows Update via GPO for my Unidesk machines and manually maintain the base OS image. I schedule the update to a couple of test VMs and I build a new VM with the new updated OS layer, just to make sure both work. Then and only then do I schedule the update to all the machines I want, with the option to boot people off of the machine if they are logged on. If I forget that last part, I get to chase my tail for a day or two getting the machines updated that have people who stay on them all the time.
It's a very small price to pay for updating all of those machines in an evening. The only applications that I know are embedded on my machines after they are completely spun up are my Forefront AV client and the Websense Endpoint Client that we push through GPO. They get updated all the time anyway, so I really can't update my base OS that often.
While you are right that by using a floating pool, you kind of remove the value of the User Personalization Layer, you still gain a lot of advantages.
1. You still get to keep exactly 1 gold image of the OS.
2. You still deploy the apps as layers.
3. You still get the storage savings.
I would even add a fourth: the machines go back to default when the users disconnect. In any floating type pool, you are going to have some sort of roaming data solution in place. Maybe roaming profiles and folder redirection from a strictly MS background, or a third party solution of some sort, whatever, so there's no loss of features as far as the users are concerned. As someone who has 15 years of dealing with those from a terminal services and desktop support model, let me tell you that I would've loved nothing more than a system that would automatically revert to original state with each reboot.
I have a floating pool built on "Unidesk VMs" that I use for remote access purposes for everyone and for our standard users in the office. I have all the base applications that we use loaded in it. I use folder redirection to send the Desktop, Documents, Favorites, and Downloads over to our storage system, then have MS roaming profiles configured for an OU containing these machines. Appdata basically is all that gets stored on the profile share, so user logons are super quick. I've even turned on Microsoft UE-V, which is so slick I just giggle every time I see it work (basically saves application configs in a central repository as XML files and pulls/pushes them back when apps are opened, closed, etc.) UE-V allows my full PC users to have their applications settings, such as their Office Themes or whatever, populate into the VDI environment automatically, giving a more consistent experience across devices.
Anyway, don't throw it all out just because you won't get the user personalization layer on floating pools. There's still a ton of advantages with it....