Mark as Asset BUT '(External)': Send (Duplicate) Selected stuff in Current Blend file to a brand new Source Blend file, Mark-Assetize it THERE instead of HERE, and convert such Selected stuff into Linked content in Current Blend file

Hello, Blenderfellows!

I love the Asset Library system, but this is in need of some big updates, isn't it? It may be bit hard to learn, UI-wise, but it's super-cool after we know some basics for projects.

This is a glimpsed of a Workflow proposition which I belive should be developed in the near future for the Asset Library system Workflows in Blender.

Currently, if we are working in a final project, say, a "Destination" Blend file (like this Starship), although it's QUITE SIMPLE (plz, check first screenshot) to turn any Linked Asset (e.g., picked from the Asset Browser, from one or more Source Blend files) into a fresh, unique Duplicate (using for example the "Make Local..." Operator), which breaks the Links (and then if we want for project re-organization, we can turn that unique Duplicate into a Marked Asset exactly in the current Destination Blend file),

the reverse is actually a NIGHTMARE to do, as there is no direct support nor Automation for it, and the workarounds are terrible (the larger the project, the worse it gets). The following screenshot just presents a 'dummy' Source Blend file after all, but the problem is that we currently have to create this Source Blend file MANUALLY, then discover a 'smart' way to 'bring' the Assets there, Asset-Mark them directly there in this Source Blend file (Greenhouse), then go back and Unasset-Mark the same concent in the final Destination Blend file (Starship), and this is super-confusing in practice. Precisely, the proposition for this "reverse" process is the following: We are working in the Destination Blend file (Starship), and then, maybe there is an Object there, or even a Collection of Objects, that we want to turn into a Marked Asset for the Asset Library, HOWEVER, we do want to 'send' the Asset somewhere else (like into an Automatically created new fresh Blend file that we might not even want to touch in principle; that's why the 'dummy' Blend file concept; why is that so difficult?), which shall then become the Source Blend file for that new Asset, meaning that, we want to be able to GENERATE ASSETS ON THE FLY/ON THE SPOT (namely, directly on the final project Destination Blend file, but having them being Automatically 'transported'/'send' to a different Source Blend file, which will then immediately also Generate the correct Linking pattern in the Destination Blend file for such Assets created in this way; Thus, it would be an 'Externally' Asset-Marked content, which should be achieved, perhaps here I think, from an additional "Mark as Asset" Operator, which would allow for this whole automation trick and handy Workflow. The last screenshot shows maybe one possibility:

I firmly believe this would be incredible to have. I don't understand the technical challenges, but I'm making this proposition because I'm not aware if there is a plan already for this; so maybe this can help improve awareness and provide some pragmatic insight into What can be done or How it might be done, from the perspective of the end user.

Thanks!