You will need to work with support to find the answers to these questions
All I'm saying is, this relevant code was "touched" in the patch - so a regression is a possibility. However, the issue could as well be caused by something specific to your environment.
Because if this was a common issue, then I'd expect at least a few other users report the same by now, with the patch downloaded a few thousand times already.