Regarding this one here:
In previous, similar issues we sometimes also had to adjust the OWSTimer.config but not only the web.config of every web application. However, the provided remediation script only covers web.config. Is that really sufficient or will we be running into issues where Workflows will still fail when returning from a waiting state and being run with OWSTimer context?
OWSTimer.config updates are only required if they have authorized types defined in that file, otherwise SharePoint would use the authorized types from the web.config for operations running on the OWSTimer process.
Recommendation would be to remove all the authorized types from the OWSTimer.config & have them all defined in your web.config. Nintex Workflow does not update the OWSTimer.config, so this would need to be updated manually in the case where authorised types are stored there.
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.