While the structure of the app internally may not have a currently loaded workspace object, perhaps it has a notion of the last applied workspace?
The app can load a workspace and once loaded, the name of that workspace is visible within the app, above the folder names on the draft list. Therefore at some level within the application, that data must be held.
I’m assuming since in the JavaScript the loading of a workspace is against the App object, that it would most likely be some correllation at that app level between it and the name and settings of the current/last applied workspace.
If there wasn’t such data being held, every time we viewed the draft list, we wouldn’t see the name of the workspace.
If I could access the name property in scripting, I could drive any subsequent tailored actions from that.