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....