It's not an X86, but in normal mode it does leave the processor for the entertainment/displays fully active.
IMO, there's not any reason ever to use the car in 'normal' mode: 'energy saving' mode saves a lot of energy at almost no cost in functionality: it can take a few seconds longer to power up the car when you get in, but usually it's done almost within the time it takes to put your seatbelt on. Turning off 'always connected' saves a modest amount more, but at a huge cost in inconvenience if you use the app for remote access.
I don't know for sure whether turning off passive entry has an effect: passive entry is certainly one of the legitimate contributors to vampire drain (ie. not down to poor implementation), since passive entry has to transmit a continuous radio signal to 'wake up' the keyfob when it comes into range. However, it appears that the system already turns this off after a couple of days - probably the explanation for the fact that leaving the car long-term has less observed vampire drain than if you took the figures for 1 day and scale up. Possibly disabling passive entry turns it off altogether.
Even with 'always connected' turned off, the embedded cellular modem is still active and signed in to the mobile network, and the car can be turned on remotely - when you want to use the app, or if Tesla want to push a software update. So if a software update happens to get pushed, you will lose some energy regardless of the energy saving settings (it will be equivalent to the 'non-saving' setting or possibly even more for the length of time it takes to download the upgrade image). The difference between 'always connected' and not is that in 'always connected' it has an open IP connection through to Tesla's servers, while otherwise it can go to a deeper sleep where the on-board computers are not doing anything, just the cellular modem waiting for 'the phone to ring' (actually, I think it's a SMS that triggers the wakeup, but I don't have evidence of that).
IMO, there's not any reason ever to use the car in 'normal' mode: 'energy saving' mode saves a lot of energy at almost no cost in functionality: it can take a few seconds longer to power up the car when you get in, but usually it's done almost within the time it takes to put your seatbelt on. Turning off 'always connected' saves a modest amount more, but at a huge cost in inconvenience if you use the app for remote access.
I don't know for sure whether turning off passive entry has an effect: passive entry is certainly one of the legitimate contributors to vampire drain (ie. not down to poor implementation), since passive entry has to transmit a continuous radio signal to 'wake up' the keyfob when it comes into range. However, it appears that the system already turns this off after a couple of days - probably the explanation for the fact that leaving the car long-term has less observed vampire drain than if you took the figures for 1 day and scale up. Possibly disabling passive entry turns it off altogether.
Even with 'always connected' turned off, the embedded cellular modem is still active and signed in to the mobile network, and the car can be turned on remotely - when you want to use the app, or if Tesla want to push a software update. So if a software update happens to get pushed, you will lose some energy regardless of the energy saving settings (it will be equivalent to the 'non-saving' setting or possibly even more for the length of time it takes to download the upgrade image). The difference between 'always connected' and not is that in 'always connected' it has an open IP connection through to Tesla's servers, while otherwise it can go to a deeper sleep where the on-board computers are not doing anything, just the cellular modem waiting for 'the phone to ring' (actually, I think it's a SMS that triggers the wakeup, but I don't have evidence of that).
The processors they have are capable of running in much lower power states (being derived from ones commonly used in tablets and achieving long standby life there), but it is almost certainly their software/system architecture that prevents them getting into low power states effectively. That in turn is undoubtedly a legacy of the rush to get Model S out of the door - where the original software builds had no power management at all and significantly worse vampire drain than we see today. It's almost impossible to retro-fit a good power architecture on a system designed without one. Whether they've learned the lesson for Model 3 remains to be seen.I think they are stuck with that and it would be tricky to move to something more economical. Not sure what the 3 runs but I'd have assumed something lighter.