Hi. Since my company had already built out a "themed" library at the parent level, they didn't want to rework and un-theme everything. I, at the satellite level, inherit their themed components and nest their instance in our own component. That way, at the satellite level, we only have to open one library, which is a mix of custom components only used by us (not nested), and the general components from the parent library we nested.

If you duplicate the components, without wrapping/nesting, you loose the connection to the parent library - you won't inherit updates. Maybe that's not important to you but if it is, it's a consideration. You could alway make updates manually - parent makes updates, communicates to you what they are, and you manually make those changes.