The thing a restart script wouldn’t catch is doing upgrades via the web from the admin panel—that’s what got me last time and prompted me to wonder if there were a fix for all cases.
I should also say: I don’t understand why the socket doesn’t get the correct context on creation. SELinux clearly knows what the default context for the socket should be, as running restorecon shows. (Also, I can see the entry for the socket made from running semanage fcontext in /etc/selinux/targeted/contexts/files/file_contexts.local.)