If you're trying to disassociate the model, you've just negated the power of top-down design, so why do it in the first place?
I can't see anything compounding, you're still only going to reference one model, one instance or another.
What you can do is step out what you would use for an inheritance as surfaces, and use that in a skeleton or assembly model.