about "never not UTC" (but otherwise unrelated to the OP):

There was an article recently, describing a very important, and also very common, "exception":

If you want to schedule/synchronize real-world appointments/events, you need both the _local time_ and the political zone, like 2018-12-11 9am at Europe/London.

The reason is that between time of entry and time of event, the defined timezone for that area may change. As a result, your previously translated appointment would not match up the local time.

Which is bad, because humans, when meeting, or events, when being announced, announce the local time. Not UTC. And they stick to the local time.