Hi, @phario and others.
How about a hierarchy of KM palettes where, with each palette, each entry has a unique first-character prefix (0 to 1, a to z) followed by – task or palette name?
That's what I do. I have a main palette with a hot key trigger (Hyper + A). Generally I trigger the target task from that palette or one of the palettes one level below. I attempt to match the single-character, unique prefixes to function, but even in cases where I can't, my muscle memory has quickly been trained.
BTW, my main palette is a combination of 21 tasks I do frequently, followed by a list of eight second-level category palettes. The 21 items have evolved and there's no requirement to limit this list to 21.
I find it easiest to use palettes rendered by the Show Palette of Macros action. Like Conflict Palettes, items can be triggered with a single key. As a nice bonus, these palettes can have a unique style.
(For months I've used @noisneil's Show a Palette of Macros - Auto-Create and Populate macro to create these palettes, but more recently I'm using a macro that I'm developing that allows one to select a set of macros using PWLs and then subsequently builds the Show Palette of Macros action using actions very similar to @noisneil's awesome macro.)