We've accumulated a number of tickets which don't fit with the main direction/goals of MicroPython (maintaining minimal code size), e.g. #2926 , #3009 , #3217, etc.

At the same time, if we'd have a special version/build of MicroPython for development testing, that at least would allow to think how to let interested parties prototype these features in the way that would be integratable and testable somewhere.

And we actually have "additional" build in Unix port, micropython_coverage. So, no talk about renaming it so far or anything, just about a path to allow to deal with the issues like above.