Historically, most people were farmers. That got automated, and yea, I guess the non-ruling classes were eradicated in the sense that we stopped having serfs and slaves and everyone became more powerful, could own land, etc. It was good news, not bad.
Complaints that there aren't enough workers in the labor market are equivalent to complaints that wages are too high. Your proposed solution is really just a restatement of the problem.
It's not as simple as UTC everywhere. If you're representing a fixed point in time, independent of any local time, then yes. But sometimes, a date/time is relative to the local time zone and in those cases, the local time zone is the correct one to store it in. For example, scheduled times for future events in the real world such as appointments. You can't store it as UTC because you can't know what the time zone offset will be in the future since that's a political decision.
What's this inconvenience you're talking about? I often don't even realize when daylight savings changes because everything is automatic. My alarm wakes me up at the new correct time, the clocks on my phone and computer have adjusted themselves. Sometimes I wonder why the clock on the oven is wrong and then Google to find out that daylight savings just happened. Maybe some people have more dependence on non-internet-connected clocks or work through the night on Sunday?