Found via a link to https://foundation.rust-lang.org/ on Derek Jones' blog https://shape-of-code.com/2021/02/07/widely-used-programming-languages-past-present-and-future/

clockspeed uses a hardware tick counter to compensate for a persistently fast or slow system clock. Given a few time measurements from a reliable source, it computes and then eliminates the clock skew.

sntpclock checks another system's NTP clock, and prints the results in a format suitable for input to clockspeed. sntpclock is the simplest available NTP/SNTP client.

taiclock and taiclockd form an even simpler alternative to SNTP. They are suitable for precise time synchronization over a local area network, without the hassles and potential security problems of an NTP server.

Blog mostly about the network time protocol (NTP).

The RADclock project (formerly known under 'TSCclock') aims to provide a new system for network timing within two years. We are developing replacements for NTP clients and servers based on new principles, in particular the need to distinguish between difference clocks and absolute clocks. The term RADclock, 'Robust Absolute and Difference Clock', stems from this. The RADclock difference clock, for example, can measure RTTs to under a microsecond, even if connectively to the time server is lost for over a week!
The RADclock is available and can be used as an alternative to the ntpd daemon to provide convenient system clock synchronisation for systems running FreeBSD and Linux. In terms of local hardware, it exploits the availability of counters such as the HPET counter or the TSC (Time-Stamp-Counter) commonly found in PC architectures.

Computer clock frequency and temperature over time--something similar to what I want to do.