I see your point, but depends how you frame it. Imagine the car would pre-load maps every morning based on some learned routine - the car knows you drive very day to work, so it will update the maps for just that. Now, if that updating wears out the storage, or simply there is a bad data in the maps causing the car computer to crash (actually happened with Tesla once), do you consider that car breaking down, or is that Tesla "removing and replacing components without your permission"? You might say "I want an option to reject map loading", ok, but then Tesla will not engage AP because the computer sees an HD map out of date, and possibly no map will even display since you said they can't load it from the internet and the car didn't come with any maps, and doesn't have sufficient storage to store entire USA map.
A simpler example would be a car automatically rebooting every night to clear memory leak issues and such. Now what if one of those reboots killed the car (boot sector is corrupt)? You could argue you could have driven it for few more days before you manually rebooted the car, so the car would break on your schedule instead of overnight, but still, it's just the car breaking down.
So, if you consider auto-update as part of normal operation, i.e. you purchased a dynamic system, then an update disabling the car is just a car malfunctioning.
All this said, I personally don't want this kind of dynamic product, unless all of these are met:
- the updates are in the background, really fast (2 minutes max), or scheduled by me
- the updates don't change the car functionality - so bug fixes, safety and security only
- updates are thoroughly tested
Maybe it's just me, only time will tell if this Tesla model of selling unfinished product and delivering over time will be preferred by people over the traditional model of finishing the design and test of a product before selling it.