electric cars have to balance how much battery they use, while parked and not being driven.
sleep states are key, but some have to be kept in a fast-wakeable state so that the user doesn't feel that the device is 'laggy'. doing a walk-up unlock is one example.
there are maintenance jobs that have to run in cars. you don't want them running while being driven, but you want them to run periodically. so, cars will raise from sleep to non-sleep states to run a job, then go back. this is normal and I don't see this going away, no matter what the brand/vendor or model (now or in the future).
network connectivity is a bit power-hungry, so vendors try to minimize how much time the 'radio' is on. in some countries (china, for example) its a legal requirement that the car sends telemetry to various (much more than one) govt agency, in order to be allowed to keep running. in the US, we have no such rules (yet..) but in china, they certainly do. I would think that the 'wake-up and report' cycle is even more aggressive in china.
tesla, as a corporation, like to keep 'metrics' on things and so, connecting remotely, getting stats and then disconnecting is common behavior, whether we like it or not. (iot is also like that, even more so, in fact).