You need to set Approver role in your Cloud Org admin console: 

You should include the launch libs into your application pages.URL can be copied from Environment Tab:  

I think that your version of Disapcther distribution is correct. Make sure that you got Apache 2.2 Win 32, example:https://archive.apache.org/dist/httpd/binaries/win32/httpd-2.0.64-win32-x86-no_ssl.msi

I don't think that it' feasible. Also, for AEM 6.1 the end of extended support is 5/31/2020

The most reliable configuration is to have S3 or Azure for a datastore.There are not many recommendations for "fail-over a shared file store".  The regular backup strategy is probably the only one.If you move to the brand new AEM as a cloud service (SaaS) you would not ever have this issue.

I think that the components' inheritance on a LiveCopy is not configured properly. I suggest to raise a support case and arrange a screen share session.

MAT did not point to the right problems. org.apache.jackrabbit.oak.segment.CachingSegmentReader is a standard AEM activity. It constantly accesses data*.tar files, hence MAT pointed to those the most common operations.Your heap dump needs a deeper analysis. You need to open a support case.

You need to configure the chunkUploadMinFileSize property of the fileupload node in the CRX repository.Please review:https://docs.adobe.com/content/help/en/experience-manager-64/release-notes/sp-release-notes.htmlandhttps://helpx.adobe.com/ca/experience-manager/6-4/assets/using/managing-video-assets...

The Connected Assets feature is not limited to AMS deployment only. We support the on-prem configuration. 

I tested in 6.5.3 and 6.4.7. I tried your steps and I have not noticed the move button turns a "grey-out".SP 7 can be accessed from https://docs.adobe.com/content/help/en/experience-manager-64/release-notes/sp-release-notes.html