Turned out that this was caused by the same caching issue as in Dec '20:
The real reason why this plugin is misbehaving is still not known, but at least now I have a quick acting medicine against this.