Thanks for writing up this response. I think you have a very good point. I am most definitely thinking of this from an Angular point of view. The only counter point I would give is that I was thinking that most of the marketing material for NativeScript would remain the same, but “Angular Native” would just be an alias used in the appropriate contexts (i.e. on Angular-related sites, at Angular conferences, etc.).
Taking a step back, let me just say that I ultimately want success for NativeScript and success for Angular. This type of change makes sense to me, but if it would harm in any way either community in the long run, I would not be in favor of it.