I'd call it a slight improvement. And after the major step back of using 2 to 4 times more memory for strings I'd call it a net loss.
> A code point string has other niceties, like being indexed by simple integers.
Again, no benefit of this. The only argument I've heard here is to prevent bad slicing and I've shown a way to prevent that.
> Also, we mustn't lose sight of what the T means in UTF-8: transfer. It's not called UPF-8 (the Unicode processing format in 8 bits).
By this argument we can't use UTF-16 or UTF-32 for internal processing of strings either. Back to code pages then.