Only BPA tool is used to check readiness to move to AEMaaCS. 

Have you tried setting up policies [1] for your parsys? Create one policy per parsys and in policy, you can configure a list of components that should be allowed for that parsys.   [1] https://experienceleague.adobe.com/docs/experience-manager-65/developing/platform/templates/page-templates-editable...

You should use AEM Best Practice Analyzer [1] tool for the health check of your custom code. The Best Practices Analyzer provides an assessment of your current AEM implementation by indicating areas that are not following AEM best practices. It also provides guidance on next steps to adopt AEM best ...

Found the correct syntax below use strict"; use( function() { var data = {}; data.id = inheritedPageProperties.get("id", String.class) || ""; return data; });

Can anyone please point me to the correct syntax to get InheritedProperty using HTL JavaScript Use API?

Now it makes sense. Please check this discussion [1], I hope you will find some direction.   [1] https://experienceleaguecommunities.adobe.com/t5/adobe-experience-manager/servlet-not-working-on-publish-instance/m-p/181364

Test the following: 1. Test your servlet on publisher directly, you can use postman for it. If the servlet is working fine on the publisher, then 2. Check dispatcher logs for any error for your servlet path 3. Also, you can try updating your rule 0107 by adding /method "POST"  

You can create a template type [1] with predefined components in it (either in structure mode or initial mode), then using this template type, Editors can create new Templates.   [1] https://experienceleague.adobe.com/docs/experience-manager-65/developing/platform/templates/page-templates-editable.h...

Request may be coming from other virtualhost in this case.

Do you have multiple virtualhosts hosted on the same server? The same request may be coming from other domains also.