I can confirm as well that the issue seems to be gone with 2.22.0 - at least the two post we had scheduled a week ago published perfectly on time yesterday and today. I‘ll continue to have a close eye on it, but for now, it seems that @Kate‘s fix really is resolving the root-cause!
Many thanks again for this amazing blogging platform and the great, responsive support!