Currently chronyd.service pulls in chronyd.service via Wants=. That's a pretty bad idea, since on my machine this delays boot-up for 20s! (Try "systemd-analyze blame" and "systemd-analyze critical-chain" to check). This is not OK, especially since almost nobody needs this at all... cronie certainly doesn't, since its even granularity is 1min anyway, so the hw RTC should be totally enough to schedule time events shortly after boot.

Shipping chrony-wait.service is certainly a good idea, but it should not be enabled by default. (In fact, currently by usage of Wants= it cannot even turned off by the admin except via masking) So, please remove the "Wants=chrony-wait.service" line from chronyd.service. (Also, while you are at it, please drop the After=syslog.target, too. syslog.target is redundant these days, syslog is available anyway for all normal services).

Please make sure to include both chronyd.service and chrony-wait.service in the systemd macro lines in the rpm spec, so that both are enabled based on the preset logic. Since "chronyd.service" is listed in the fedora preset file it will be enabled on all new installations this way. And since "chrony-wait.service" is not listed there, it won't. However, if an admin decides that he wants to enable chrony-wait.service globally on all his systems he can drop-in a additional preset file that also enables "chrony-wait.service".