Work on registry and aws-native has probably distracted developers from extending awsx. There is a roadmap for it, which probably leans towards making it available in other languages.

Since aws and aws-native are complementary, I'm betting that a migration off aws onto aws-native is very low priority. There would be no visible improvement to awsx users from this change. The only pressing reason to do it would be to enable the deprecated of aws, and that's not likely to happen any time soon (too much code is dependent on that).

With the addition of component packages in the registry, adding a separate awsx-native package is feasible and probably more likely than changing the existing awsx package.

All the above are my own hypotheses and in no endorsed by Pulumi.

I believe that supporting additional languages in awsx is quite high priority in Pulumi's plans, though unscheduled as yet. Other upcoming changes that relate to awsx include "v2" (no idea what that means) and enhancements to multi-language components (which might bring aws-native and "v2" together?).