No need to be rude. >_>
I actually see your problem here. You want the edits on your current workspace to propagate to all other files you are working on (workspaces stored in the program, not the files). While that is desireable in some cases I also like that Blender is able to save workspaces to a file. It’s a different kind of thinking. Also it’S not as easy to screw up your workspaces once and for all and for all your other files. That’s something I did in Modo more than once and it it was annoying as hell!
Bringing it over to the program side would probably screw up the work for many others. I kinda like @julianeisel’s proposal where an addon is able to propagate it back and forth to a central file. This way would make it a little less immediate to work with as you’d need to load in a file from the main workspace automatically. It would keep the existing compatibility and add another layer for people who work with layouts a lot, on top.
I’d imagine something like this:
The individual .Blend files should be saved somewhere like the Startup files, maybe.
This would mean that you’d have to hit ‘load’ on a file where you have an old layout in use but it would mean that it’s just the click of a button and would not break logic for existing users.
Maybe you could even throw in an Auto-Load button that updates the workspace based on the name on loading up a new file. That would be a ‘sort of’ global workspace equivalent with the added bonus of having to use it globally on top.
Don’t know if that’s easy to implement, though. I’m also just a user, not a developer. 