AND, when importing layers, can the root layers not needing to be duplicated be ignored, such as Construction/Dimension, and so on?

When two files have the same layer construction, and I want to import a whole tree, I'd like to be able to. I'd like for there to be an interface similar to in Filemaker/Lotus Approach/other databases, where there is a row-by-row, left-right column view with arrows to select/de-select which layers come in, which overried the target, and which defer to the target, provided Shark is able to "deconflict" geometry issues prior to accepting and committing a commanded change/import.

It would be stellarly awesome if, when working between/with two VCP/Shark/Slt files, the copied object had an ability to carry with it all of its layer structure, which could be plopped into a VCP/Shark drawing. It would save tons of hours of manual recreation of layer info when xrefs is not wanted.

Speaking of xrefs, can xrefs' "binding" also drag in the entiies' specific layer structure? If a piece of geometry is selected and copied and pasted into another VCP/Shark file then "encapsulization" of the geometry's layers could be a type of "snipping/cutting" and then be placed on a particular layer tree or branch of the user's choosing.

Then, if needed, the user should be able to cut and paste branches or twigs or stems into other layers. Even any layer should be able to become a separate or top-level layer for drawing reorganization purposes. Mid-stage drawings that get repurposed cost a lot of time "merge" into another, new base-level drawing. And, when I make a mistake and structure a layer in opposition to a previous task, it's painful to reconcile things.

I'll scrounge up $100+ just to see that facility in the next upgrade, especially if it happens within the next 4 months.