You can contact the support team or your Adobe representative in the account to find out whether the feature is in the roadmap or not. 

You can first test the resolve function in resource resolver mapping testing console. Open this url - http://localhost:4502/system/console/jcrresolver, put "/en/test.html" in the text box and click on resolve button. If you don't see a mapped resource listed then the API method will not work. You wi...

I will still recommend that you migrate only the mutable paths via oak-run utility and not entire repo.

You can consider embedding the form using a javascript code on your app. Please see this documentation for more details - https://experienceleague.adobe.com/docs/experience-manager-65/forms/adaptive-forms-basic-authoring/embed-adaptive-form-external-web-page.html?lang=en#best-practices 

You can get the reference to a resource from a shortened absolute path. The API method for that is resolve() which does a reverse mapping of path to resource - https://helpx.adobe.com/experience-manager/6-5/sites/developing/using/reference-materials/javadoc/org/apache/sling/api/resource/ResourceReso...

It looks like there are some system packages which were not installed properly on Linux. Are you using Adobe Forms as well on your Windows machine? Adobe provides separate packages for Forms based on the target OS. I would recommend that you first do a basic Vanilla installation on Linux and then co...

You can use ACS common Page Relocator tool of ACS commons to rename pages in bulk https://adobe-consulting-services.github.io/acs-aem-commons/features/mcp/subpages/tools.html  

You can setup the new AEM sandbox on Linux OS and to migrate the repository content you can use the oak-run utility. You can find more details in the following doc - https://jackrabbit.apache.org/oak/docs/migration.html 

Just got to know that someone is seeing similar performance problem with 6.5.7 running on RHEL OS. They have logged a ticket with Adobe support.

Another option is to rewrite the API url on the live page JS code so that it passes the page size as a selector in the URL. Like - /api/assets/cf.150.json. And then you can add a rewrite rule in Apache to remove the selector and add it as a query param before it passes the URL to AEM for processing....