I suspect there will be a lot of customized stuff that we end up with when we actually do the import (though to be fair, while I think NodeBB is our leading candidate, it's not a done deal yet). We did a partial import from CS to Discourse, so a lot of the user deconfliction has already been worked through.
@Joykiller Not sure if you're around anymore but I thought I'd respond anyway.
The problem with maintaining a plugin and theme directory is the maintenance aspect. We simply don't have the time to make sure everything is compatible, especially since every plugin created is a community contribution.
So we automate. We rely on plugin developers to report plugin compatibility, and serve only those plugins that are marked compatible. There is one downside, however, and that is plugins will quickly disappear in successive revisions of NodeBB unless the authors keep them up to date.
So there's definitely space for crowdsourcing as well. If a plugin is not marked compatible by the developer directly, multiple reports of compatibility by the plugin users should also count, and if enough votes come in, then the plugin should automatically be reintroduced.
☝ that part isn't in yet, but it's on the wish list.