> Those funds would then be distributed by usage - every mention in a package.json or requirements.txt gets you a piece of the pie.

Usage is not a good proxy for value or ongoing effort. I have a npm package with tens of millions of weekly downloads. It's only a few lines long and it's basically done - no maintenance required.

I'm skeptical that there exists an algorithmic way to distribute funds that's both efficient and resistant to gaming.