No need to be offended. I've clearly advocated Unicode16, which surely encompasses your spelling. Unicode16 is an achievable and implementable goal. I welcomed it as a great advance.
I do note that you use ASCII for your handle. Could that be because few will be able to figure out how to enter the code point for your name? If your handle includes code point 0x123456, how do you expect users to deal with it?
I only use an ASCII handle because this forum is English only and I don't want to waste my time answering stupid questions. My Korean colleagues can type Korean handles just fine, thank you for the consideration.
But still. I'm fortunate that my Korean name does fit in 2,350 common Hangul syllables, but there are people aren't (who are greatly disadvantaged). And way more Chinese and Japanese people have rare characters in their names. I even have a concrete data for them; the Japanese goverment defines the Koseki unified character set (戸籍統一文字) that complement common character sets and are intended to be used for family registers (戸籍). Therefore it should cover most person and location names ever used in Japan (and probably nothing else). There are 44,770 characters in this set, including 857 characters not yet encoded to Unicode [1]. So the reasonable character set supporting most Japanese proper names already require more than 50,000 distinct characters!
Unicode16 was never ready for long tails. The Unicode committee only realized this after a massive number of character assignments, which is their only regretable mistake in my opinion.
I do note that you use ASCII for your handle. Could that be because few will be able to figure out how to enter the code point for your name? If your handle includes code point 0x123456, how do you expect users to deal with it?