The first bit is wrong, but you take the biscuit with .....
"Another last ressort is each subscriber wil have a class of service so they can use that to conserve the batteries. Ordinary subscribers would get cut of first then businesses and less critical users such as OAP homes etc"
Utter tosh.
Now, I may only be a software engineer, and worked on AXE-10 systems for mobile rather than fixed-line installations, but I did get a good grounding in the overall system design in my years at Ericsson.
In all that time, I never came across any way that the system could shed power load gradually. Yes there were ways to reduce traffic load, but not power.
Knowing the way that the system is designed, there isn't a way to reduce power to the group switch, or to any of the central or regional processors, or to any of the trunk hardware. The only way to reduce power to certain subscribers would be to concentrate critical subscribers onto certain hardware, and cut power to the remainder; but (a) I haven't seen that capability, and (b) that goes against the principle of spreading your critical subscribers over different hardware in case of other failures.
At the software level, on the mobile side, there was a lot of effort put into certain robustness & recovery features, to cope with failures etc. But I can say for a fact that extending operation time when on battery was not one of them.