No, unfortunately none of the suggestions were specific enough to be of any help, they tended to be general AEM troubleshooting pointers which we'd already tried. This appears to be an issue that is introduced when the Adobe Guides install is included in the project via the Adobe Guides Git Pipeline...