As much as it sounds like a good idea, it's definitely difficult to use for me. Here is one example. I have a project loaded with all the instruments and like layout. I save it as custom Lens. Save the project and later add another instrument to the and adjust the Console add a few tabs to the multi-dock.
Next time I load the project the custom lens "wins" over the project settings and all post-lens-save changes are lost. This means I'd need to additionally save a custom lens for each project to have it work. I'm not sure what they were thinking or attempting to accomplish. It's definitely confusing to use "as is". Right now I cannot figure out to save a project without the custom lens. It comes back after save, even when choosing "none" before save.
I regret trying it. Making a mess of things and I cannot get it out of my project.
EDIT: if Lenses were "global macros" that did not change project (tabs, console channel strips, etc) and only used to arrange the work space into pre-defined screen sets that might be slightly more convenient that the earlier work space management. Having the lens be saved within the project and additional take precedence is just wrong imo.