What are you looking to gain by putting a separate Tealium profile up for a subset of the site's pages?
If you just need to have separate metadata for "shop" vs the rest of the site (variable values, events, etc) and want to use the same Coremetrics profile/client ID, you should generally be able to modify the analytics implementation for the new "shop" pages independently from the "content" and "videos" sections by using conditional logic in your extensions.
For example in a "Set Data Values" extension, you can add a condition like "if URL contains "/shop" or domain equals "shop.example.com".
Since you want to use the same Coremetrics profile across both "shop" and the rest of the site, that approach would be easier than having two separate Tealium profiles.
If you need to configure the actual Coremetrics tag differently for "shop" vs the rest of the site (ie, different client ID, tag version, collection domain, etc) you can use Jim's approach above .
Hope that helps!