Hi,
Good questions. Regarding the builds I personally have no opinion about that, since I do not understand or have insight in the implications of the different choices.
When it comes to the features, I have actually been thinking about exactly the same.
I realized for example that I had missed the Papyrus_RT Core C++ Feature, which is not included in the top level Papyrus-RT Feature either. This makes perfect sense also, since the bringing in the specific language feature should be optional (depending on which languages we should have). We had a discussion in the mailing list a while ago, about exactly this, and I made a simple picture back then
I guess in the same way as we want to keep the C++ (or C or Java and so on) as optional features, we should also have the import tool a separate feature, not included in the top level Papyrus-RT Feature.
So I would propose to move the new import feature as separate feature as well. If you have the need to import old RSARTE models, then you need to check one additional feature (apart from the action/target language that you want to use).
/Peter Cigéhn