I can't say that I'm against it, especially now that it's been fleshed out a bit more with the other types you gave examples of. 
My initial hesitation was to the Character type specifically being treated differently from other strings or scalars, but I think if we partitioned the various types by their cardinality and said:
- Single quotes represent literals that can be treated as a single ASCII code unit, UTF-16 code unit,
Unicode.Scalar, (edit: orCharacter), depending on the type it's being coerced to - Double quotes represent literals that contain may only be coerced to types that support multiple characters
...then we'd be telling a consistent and compelling story.