The issues I stated above in regards to whonixcheck and sdwdate not responding were due to the msgcollector.service being in the wrong location (/lib/systemd instead of /lib/systemd/system).
Once I placed the msgcollector.service in place, I did receive an error that it could not mount
May 17 02:48:42 host systemd[1]: msgcollector.service: main process exited, code=exited, status=3/NOTIMPLEMENTED
May 17 02:48:42 host systemd[1]: Failed to start msgcollector.
May 17 02:48:42 host systemd[1]: Unit msgcollector.service entered failed state
Running /usr/lib/msgcollector/msgdispatcher_init directly gave me the error:
root@host:/lib/systemd/system# /usr/lib/msgcollector/msgdispatcher_init
mount: wrong fs type, bad option, bad superblock on none,
missing codepage or helper program, or other error
In some cases useful info is found in syslog - try
dmesg | tail or so.
I then proceeded to comment the line mounting the tmpfs, and was able to start the msgdispatcher service and at that point whonixcheck worked, but I can see sdwdate is not implemented. No dialogs appeared, but I assume you are aware of this already.
As for the other issue of services not being enabled, I don’t know why still, as you may have notices I always enable them in postinit script.
Anyway, this is good news that I believe the Qubes build has working whatever is already implemented.
To bad I don’t fully understand the business logic of msgdispatcher or sdwdate or I would have fixed them and I now will have a few hours of down time until you release next development-version.
I have tomorrow available to work on any issues if there is anything that won’t take you longer to explain how it works than to implement it yourself 
