OK, testing the "Delay startup of FTL earlier to avoid database importing issues with incorrectly configured fake-clocks" change in the beta. I added DELAY_STARTUP=5 and then forced it to boot without fake-hwclock. These log entries show that it was 12/31/1969 when FTL startup script started, and 7/4/2021 at the end of the 5 second sleep:
[1969-12-31 18:01:02.571 1651M] Finished config file parsing
[1969-12-31 18:01:02.571 1651M] Sleeping for 5 seconds as requested by configuration ...
[2021-07-04 14:04:17.390 1651M] Done sleeping, continuing startup of resolver...
But still getting the warning (now the New warning):
[2021-07-04 14:07:52.965 1711M] WARN: Found database entries in the future (1625425500, last: 3300). Your over-time statistics may be incorrect
[2021-07-04 14:07:53.001 1711M] New upstream server: 188.8.131.52:53 (0/1024)
[2021-07-04 14:07:53.002 1711M] New upstream server: 184.108.40.206:53 (1/1024)
Should the Delay startup change that was made to FTL have prevented this?