Keyboard Maestro scans the ~/Library/Logs/DiagnosticReports when the editor launches looking for reports that start with “Keyboard Maestro” and end with “.crash”. Do such files exist?
I have in fact received that crash report, although it does not have an email address associated with it - check your Keyboard Maestro General preferences and see if it is set to Always send your diagnostic reports.
I also have four others over the last four months from you with the same crash issue.
That crash report is pretty easy to read in broad terms:
Thread 0 Crashed:: Dispatch queue: com.apple.main-thread
0 libobjc.A.dylib 0x00007fff595dde9d objc_msgSend + 29
1 com.stairways.keyboardmaestro.editor 0x0000000100d3f0dc NewScrollWheel(NSScrollView*, objc_selector*, NSEvent*) + 221
2 com.apple.AppKit 0x00007fff2f8f056f forwardMethod + 211
3 com.apple.AppKit 0x00007fff2f9da368 -[NSView scrollWheel:] + 359
4 com.apple.AppKit 0x00007fff2f8f056f forwardMethod + 211
5 com.apple.AppKit 0x00007fff2f8f056f forwardMethod + 211
6 com.apple.AppKit 0x00007fff2f9da368 -[NSView scrollWheel:] + 359
7 com.apple.AppKit 0x00007fff2f8f056f forwardMethod + 211
8 com.apple.AppKit 0x00007fff2f8f056f forwardMethod + 211
9 com.apple.AppKit 0x00007fff2f9da368 -[NSView scrollWheel:] + 359
10 com.apple.AppKit 0x00007fff2f8f056f forwardMethod + 211
11 com.apple.AppKit 0x00007fff2f9da368 -[NSView scrollWheel:] + 359
12 com.apple.AppKit 0x00007fff2f8f056f forwardMethod + 211
13 com.apple.AppKit 0x00007fff2f9da368 -[NSView scrollWheel:] + 359
14 com.apple.AppKit 0x00007fff300bc43d -[NSWindow(NSEventRouting) _reallySendEvent:isDelayedEvent:] + 5040
15 com.apple.AppKit 0x00007fff300bac70 -[NSWindow(NSEventRouting) sendEvent:] + 497
16 com.stairways.keyboardmaestro.editor 0x0000000100d903a0 -[IntegratedWindow sendEvent:] + 142
17 com.apple.AppKit 0x00007fff2ff1c0d6 -[NSApplication(NSEvent) sendEvent:] + 2110
18 com.apple.AppKit 0x00007fff2f77c87d -[NSApplication run] + 812
19 com.apple.AppKit 0x00007fff2f74ba3a NSApplicationMain + 804
20 com.stairways.keyboardmaestro.editor 0x0000000100b2e3db main + 155
21 libdyld.dylib 0x00007fff5a206015 start + 1
Basically it is crashing in response to the system going nuts with the scroll wheel processing. Other than your five reports, I have about 20 others over the last 12 months (probably since the release of version 9) (so two crashes per month total on average). Reports are not limited to 10.13, but happen on other versions of OS X as well.
If you can determine exactly when using the scroll wheel crashes, in a reproducible way, that would definitely help narrow down the cause.
But this only explains five editor crashes in about as many months - not something I'm happy about, but far less than what you are describing in terms of problems.
It doesn't indicate any crashing creating macros (unless you just mean crashing in the editor generally when using the scroll wheel).
And this would not have anything to do with “macros are not executed but aborted”, and I don't know what you mean by “macros like KMFAM cannot be installed”.
“But maybe one more thing: I have to do a SMC reset at least 2-3 times a day because KM causes problems.”
I don't even know what that means - what on earth would require an SMC reset? And how is it related to Keyboard Maestro? Resetting your SMS should be a last resort - I don't know that I have ever done it myself, I can't recall ever suggesting it as a good idea for anyone.
You say “the list of enumerations is long” - but a) you need to solve one at a time, they are not all related, and b) without enumerating them they cannot be solved.
There are thousands of people running Keyboard Maestro 9.x still on 10.13, and I get no stream of reports of issues, so problems in general should be either rare, or specific to particular situations.
As far as this crash goes, if you can narrow down the cause, which is related to processing a scroll wheel event and probably depends on exactly what is shown or exactly what the mouse is over at the time, then I can look in to it further (and I will do my own investigation as well to see if I can figure it out).
As far as everything else, you need to deal with one specific problem at a time, there is not likely to be any kind of systemic issue.