He uses Chrony, which uses system time, and compares those times across different machines. Unless proper setup is done the benchmark is faulty.
Making the sync work across existing heterogenous hardware is the goal of the exercise. That can't be a disqualifier.
It’s easy to fire up Chrony against a local GPS-backed time source and see it claim to be within X nanoseconds of GPS, but it’s tricky to figure out if Chrony is right or not.
"system time as distorted by getting it to/from the network" is exactly what is supposed to be measured here.