Changing your assumption of "default state" doesn't change what I said.
The point is that systems like this go through various analyses before being built. Reliance on outside services/components is one of those analyses.
Let's say that a critical component is an online service. Someone will do the analysis of what happens when that service goes away. If the outcome is that you can expect to failover to something else with acceptable degradation of performance, then the service might be used. If not, then the choice is find a more reliable service, build it yourself or do without the feature. And those last two choices will themselves be subject to another analysis.
One of the nice things about capitalism is that if there's a profitable gap in products/services, that gap will eventually be filled. All new CPUs need to cloud connected and require a service provider, but there's a big industry that can't deal with that? I guarantee that someone will corner that market and start building CPUs that don't need to be cloud connected and require a service provider. Either that, or sufficiently reliable cloud services, tailored to that market, will appear.