To be honest guys, this will cause way more problems then gains.
The idea, can try to find references on github, is to change the representation of time on dom0, and keep qubesos and all vms having time representation in UTC.
This way, users are supposed to change the dom0 clock widget timezone when they move around (their timezone) and let the system clock, and all vms and logs, operate and log in UTC.
The reasoning is pretty simple if you think one second as a computer. UTC/GMT timezone is 0. Without daytime saving whatever, and the system is always having a straight storyline for logs and everything else. Otherwise, if you instruct your system to store system time in local timezone, a bunch of bad things can happen. For example, when cames the time to lose an hour, that is, putting the clock of your computer back an hour ago, logs alone will live the same hour a second time that day. Not good. And also, when it’s time to move the clock one hour later, there is a time jump in the logs. This is why computers generally keep system clock in UTC/GMT timezone, and rmwhen comes the time to do some auditing, a quick check up of what is your time offset difference does the trick.
Also, when comes the time of using time based tools, for example TOTP, the app on your phone, and your computer as well, will be in system time UTC, and the TOTP app, to be able to generate a code that fits in both computer and phone which generate it, needs to be generated/showed/confirmed in the same timezone. Your phone takes the time at UTC time, and for this to work, your computer clock, system time, also needs to be in UTC. Otherwise that won’t work. Keep system clock in UTC.
Tldr: you can ask your dom0 widget, or configure through timedatectl the time representation to be in your timezone (ex:UTC-4, EST) which will automatically change the dom0 widget as well, which offsets from system time here.
The whole thing happening here is that through the installer, timezone was set. So if you play without following documentation you will screw time big time.
I recommend not messing with time, and only changing time from dom0 widget.
- Official documentation points here Changing your Time Zone
Note timedatectl status:
RTC in local TZ: no
Click on widget, revert changes you did, never do that again 
time is… A weird concept even if not mostly for computers which are always lost unless synced with an outside source and can easily time warp if misconfigured.
Always change time zone representation, not system time. Only ntp should do it and again, in UTC for system. Time.