For dnscrypt, incorrect time will cause failures. I don't know what the time tolerances are here (i.e fast/slow by minutes, hours, days, etc.), but at some point the uncorrected clock drift can certainly cause issues. And, once dnscrypt starts, if the local resolver is reliant on it, the moment that drifts out of tolerance, you'll have a chicken or egg problem getting time to sync up again (as described here for EdgeMax/Unifi).
Sorry. Missed a couple details 
see edit.
I expected the same
Yes 
. Rereading the thread is somewhat embarrassing in retrospect.
Thank you all for your assist