Sure; I was reacting to the specific concept of a "non-Unicode-squiggle", implying that the character has no known mechanism for encoding it (i.e. it's not simply an SJIS squiggle) and would likely have to be submitted as a custom bitmap/vector path. That's a good place to draw the line.
The whole point is that there are characters in use in certain languages that have accepted mechanisms for encoding in some non-Unicode character encoding system used for that language, but not in Unicode.
