From some light-testing on a local instance installing the Hotfix won't break 6.4.It brings the minor version up from 1.2.60 to 1.2.100.There's virtually zero active development within the CRX space of AEM. It's a very mature part of the product. So changes across AEM versions is generally minimal. ...

Hotfix-GRANITE-30226-1.0-1.0.1.ziphttps://documentcloud.adobe.com/link/track?uri=urn:aaid:scds:US:de812fad-c373-4c67-bd34-a6f0b2506434 NOTE -- you will need to use Firefox or some other non-Chrome browser to install. NOTE -- this was built for AEM 6.5 

When you manually touch a config via ConfigMgr in the OSGI Felix Console it will create the config as a nt:file node under /apps/system/config . It's not touching the pre-existing sling:OsgiConfig node or config file. You can see which configuration is taking precedence here : http://<host>:<port>/s...

How deep is the path to the config?  The JCR Installer (org.apache.sling.installer.provider.jcr.impl.JcrInstaller) by default only looks to a max depth of 4. 

Can you share the output in the error.log from the HTML Library Manager? It likely spits out some more details on why the minification fails. Can you manually minify your JS directly on Google Closure? Here : https://closure-compiler.appspot.com/home

jsProcessor=[default:none,min:gcc;languageIn=ECMASCRIPT_2015;languageOut=ECMASCRIPT_2015]

With the Dispatcher log level at DEBUG can you share the log output for the vanityUrl request?  Do you have the vanityurls component installed?It's an old package from 2015 that oddly enough doesn't come with the product ootb. 

Changing the logging level of the ROOT logger is tricky and often necessitates a server restart. This is also going to spit out GB of logging data.

RE : Please provide me the hot fix to resolve this problem. AEM 6.1 is end of life.   That error just implies that the bundle is not active. Go to system console bundles and restart - com.adobe.cq.cq-experiencelog

Is your SAML set up as Idp initiated or SP initiated?If it's SP initiated then that Oak login token approach won't work since the session is never invalidated with the Idp.The Idp will log you right back in.