AFAIK SP1 should have fixed it. If not it is known bug in 6.1.   Please create a node /etc/replication/treeactivation with properties [1] & will fix the issue. [1] "jcr:primaryType": "sling:Folder","jcr:title": "Activate Tree","title": "Activate Tree","sling:resourceType": "cq/replication/components...

The symptoms indicates there is another workspace created may be due to change in repository path or OS level file system issue.  Attaching the logs to daycare before & after issue occured could lead to find the operation that caused it.   Most of time I have seen is due to new team doing an install...

if it is upgraded instance OR the page is custom one & not geometrixx . It is due to changed  less compilation implementation in CQ5.6 onwards. Validated your .less file and fix import as required.   If above does not holds good reach out to official support request.

Install Sp3 will fix issue https://docs.adobe.com/docs/en/aem/6-0/release-notes-sp3.html

Scaffolding is used to create a large set of pages and allowing it to upload directly can make multiple copy of same asset in all newly created page. It does not sound good design.  Recommendation is to upload in dam and reference it so that you do need to duplicate on all newly created page.

It will work. Please go through step by step tutorials provided at https://github.com/Adobe-Marketing-Cloud/aem-ldap-tutorial

SP1 coming up shortly will have the fix. Watch out for sp1 release.

does three custom property name contain any namespace?  If so create that namespace,

It various from case to case. Please get a couple of thread dumps when taking longer time, analzing it will give you a clue.   Or you can file daycare ticket with all the logs and thread dump will analyze if you are not familar with thead dump analysis.     Couple of scenario where I come across was...

Upload is just an creationg & not modification. Also asset get modified at time as rendition creation etc...     For your use case update the workflow launcher to trigger the activation.