Hi, @alexherbo2!
You do have some interesting ideas here. Leveraging already available Kakoune features (the module system and the autoload directory infrastructure) to do the job seems the right path to take on the plugins story for Kakoune.
Nevertheless, open source projects are always a balance between innovation and agreement: it’s much easier and faster to go alone, but together we go stronger.
Thinking a bit about your proposal, I see a problem on it: for it to work the way it’s meant to, you must convince every plugin developer to wrap her plugins inside modules. You could convince some, others would prefer to stay the way it currently is, and suddenly our small community would be divided between the modulers and the andreyorsters.
I think that, since Andrey left the project, we have a unique opportunity to design the future of plugins machinery for Kakoune together. For that I’d kindly ask you and @robertmeta to, together, start a discussion about it, inviting all stakeholders to take part on it and give their thoughts, from plugin developers to end users, including also Kakoune developers.
What I would really like to see is an agreement on best practices for developing plugins and, with hope, a unifying approach materialised on a single plugin manager implementation with (why not?) a dedicated Github organisation which everyone interested could join, in the lines of what we already have for kak-lsp.