Unfortunately I can no longer point to a canonical "best practices" configuration as the original has been neglected; however it may serve as a starting point: https://github.com/SwiftOnSecurity/sysmon-config
Yes. Newer versions of Logstash have an on-disk queue that will store events that haven't been ACK'd by ElasticSearch.
On the other side, every Beat (or nearly every Beat) can write to a messaging product like Kafka. That allows you to get logs off your client in the face of failures in either Logstash or ElasticSearch.
https://github.com/MHaggis/sysmon-dfir
As of September 2017, v6.1 supports monitoring WMI subscribers.
https://rawsec.lu/blog/posts/2017/Sep/19/sysmon-v610-vs-wmi-...
Unfortunately I can no longer point to a canonical "best practices" configuration as the original has been neglected; however it may serve as a starting point: https://github.com/SwiftOnSecurity/sysmon-config