What does that mean?
You should try it. Configure a template canvas using the designer GUI to have the pieces you wish, placed as you wish. Copy the resulting dataset into a tag. Point a window with tagpath parameter at that tag, and bind the root container dataset to drive the template canvas.
It sounds like you're deliberately trying to avoid templates/parameterised popups in favour of creating a 1:1 ratio of these for your tag instances.. You're going for simplicity, but at the end of the day if you ever have to modify something in all of your individual popups, it will be an absolute nightmare having to go through each and every one (take Paul's advice - it's near impossible to edit the xml yourself). The maintenance cost will be huge (not to mention the toll on sanity).
So often I see projects, mostly in other platforms and from oems, where they have created a valve popup and then just duplicated it for as many valves they have in the system (they also make sure to move some of the objects by a few pixels in each of them for some reason 
), instead of just using a single parameterised popup. Nightmare!
I am looking into it. But i fully intend on manually organizing and adding to each window. As long as this dynamic window works for all future projects as long as my naming convention stays the same then ill be good with moving forward with it. Without having to be modified. My initial intent was 1 window per folder in tag browser, 1 image per window, 1 I/O template per device, and 1 motor template per motor. This would be something i click 1 button give it my tag json file and it does the rest.