There's another factor much on my mind. A while ago Peter talked about the size of the plist file (Keyboard Maestro's macro file), which I think I discussed in the documentation for Brevis -- Automating Text Expansions.
So, as a matter of ingraining best practices, I've been looking at different ways of constructing a macro to save space.
I've been surprised that there's not much penalty for using a Custom HTML Prompt over a Prompt with List, even tossing in CSS and JavaScript. And the jury is still out on subroutines, which I thought would be a slam dunk.
No doubt that should be balanced against the time it takes to put things together as well as performance issues.
But for me, the smaller my plist, the more time-saving macros I can indulge in without penalty. (And, yes, it does seem to be therapeutic!)