Thank you for this Chris.
Has this been implemented? I'd love to trim the fat off of large macros.
Also not directly related it is worth noting that disabled macros will still run via a subroutine and only disabled the trigger. However Keyboard Maestro is inconsistent in it's behavior and a macro is called via AppleScript it will not run. I guess in some ways you could say AppleScript is the trigger and this could be helpful so you can choose if you want to call something via a subroutine or via an AppleScript but @peternlewis doesn't garentee this behavior will remain the same.
Apps like CommandPost show all of Keyboard Maestro's macros and I suspect it calls them via AppleScript since when they are disabled they do not run.