This is similar to how HAXsite's can load stuff out of the custom directory and have their own customized build routine. The wc-registry supports multiple registries so either..
we could inject an additional one if one exists
we could do a similar custom build that gets globbed in with everything
A would be faster than B but A wouldn't be as portable (download a site, you won't have those assets... unless the deploy itself is a cdn)
B would load everything at once which could be a lot more to load and if a theme is a stock one you are needlessly loading all those additional assets.
Unless a theme was designated as core vs implementation specific. At that point you could define that this theme requires loading the additional assets. This doesn't account for loading additional elements that are non-theme in nature, which would be more in favor of A over B.
This is similar to how HAXsite's can load stuff out of the custom directory and have their own customized build routine. The wc-registry supports multiple registries so either..
A would be faster than B but A wouldn't be as portable (download a site, you won't have those assets... unless the deploy itself is a cdn) B would load everything at once which could be a lot more to load and if a theme is a stock one you are needlessly loading all those additional assets.
Unless a theme was designated as core vs implementation specific. At that point you could define that this theme requires loading the additional assets. This doesn't account for loading additional elements that are non-theme in nature, which would be more in favor of A over B.