This is available in 6.3 as well. Here is the doc - https://helpx.adobe.com/in/experience-manager/6-3/assets/using/mac-api-assets.html. Are you not able to run it on 6.3 ?

Here you go- curl -u admin:admin -X MOVE https://[aem_server]:[port]/api/assets/source/file.png -H "X-Destination: http://[aem_server]:[port]/api/assets/destination/file.png" -H "X-Overwrite: T"CopyReference - https://experienceleague.adobe.com/docs/experience-manager-65/assets/extending/mac-api-ass...

Yes it includes fixes of previous version as well. That's why it is called as cumulative fix pack. 

Instead of using granite render condition you can write custom JS code to make the checkbox read only. Example - var checkbox= $("[name='./hideInNav']").adaptTo("foundation-field"); checkbox.setDisabled(true);

You can hide a check box using a render condition and not make it read only. Render conditions are evaluated server side by Granite UI framework to show or hide a UI component. You can write a custom render condition to hide the checkbox based on the resource type. For more details see the following...

You can use the Asset Ingestor or URL Asset Importer utility of ACS commons package. More details can be found here - https://adobe-consulting-services.github.io/acs-aem-commons/features/mcp-tools/asset-ingestion/index.html 

We tried moving the component design dialog stuff to /conf but it didn't work. We have not yet migrated to editable templates yet and therefore we will have to continue with the design dialogs. Also, if we keep the design in /etc then how we can activate the design as there is no miscadmin UI and I ...

You can configure the search forms of Assets Admin UI and add the pattern for exclusion in excludepaths predicate property. http://localhost:4502/libs/cq/core/content/tools/customsearch.html/libs/settings/dam/search/facets/assets/jcr:content  For more details refer this documentation - https://exper...

I don't think it will work even if you enable the feature from UI after customization. The backend implementation logic of Launches use PageManager and MSM APIs so I don't think it will work on product data. 

I would recommend you to do a content freeze while you are doing an upgrade in production. When you move content or workflows from 6.4 to upgraded instance then you basically bring in data which has not been in place upgraded. The in place upgrade utility will make sure to update any properties on t...