As a preface, I searched for information regarding this circumstance ad nauseum before posting, and could not find any info relevant to this particular concern.
I have two different sys-net qubes. One I use for web browsing, general use, etc. The second sys-net qube I use only for updates (via Tor), upstream from both a secondary sys-firewall and sys-whonix (respectively).
I set my clock qube in global config to correspond to the sys-net qube that is only used for updates as I am under the assumption it would be more critical to have accurate time sync for torified dom0 and template updates.
My machine isn’t spec’d out enough to run multiple sys-net qubes at the same time. I have noticed a clock lag of around 1.5 hours in the time and date on my dom0 taskbar.
Is this a cause for concern? Should I have my clock qube set to correspond with my general use/browsing sys-net, or should I leave it as I have set up now?
To clarify, is the lag always 1.5 hours? This sounds like problems with timezone settings rather than clock sync setting (or hardware RTC issues). Please run timedatectl in dom0 terminal and look for TIme zone to assure if it is right.
There might be issue with outdated tzdata for your area since Fedora 37 (used for dom0 in Qubes r4.2) does not receive updates for it for a a while. I appreciate if you could run timedatectl once more and assure time difference between UTC and your area is accurate.