With 4 and prior, I had run ntpd on OMV for years. I ran it on my OMV machine to allow all my other devices to get their time from it since it is the only machine I have running 24x7. It was never a problem and it worked well.
I upgrade from 4 to 5 and see that the upgrade has removed ntpd. I figure the install has removed it to go back to the OMV default. The OMV installs sometimes do things like this. Should I have read the apt output carefully before proceeding? Yes, in fact I said so in my original post. So yes, it is my fault, but my experience with ntpd working on OMV for years had me assuming it would continue to work. The behavior has changed.
All I was asking for was a short statement that contains "ntp" or "ntpd" in the docs, maybe release notes, that would help others avoid this, for example "OMV uses chrony for time synchronization. ntp/ntpd is not supported and should not be installed." Yes, you'd have to maintain that one line in the docs and yes it would need to be removed if the chrony to ntp switch were ever undone. I'd be happy to contribute a pull request on the docs (or however the docs are changed) however since that's been pre-rejected, I'll not spend that time.
Thanks for your thoughtful responses to my request.