
Hi Chris,
Sorry but we don't currently have logic in there to determine which identifiers are type names (compared to namespace names, other identifiers, etc.). That would require us to run the resolver on every single identifier constantly as typing occurs, which unless done asynchronously, would be too impactful on performance.
As for changing colors, yes we have a Highlighting Style viewer QuickStart on that in the sample project under: "SampleBrowser\ProductSamples\SyntaxEditorSamples\QuickStart\HighlightingStyleViewer". But we just noticed that due to a recent update in how BrushEditBox works (used in that sample's HighlightingStyleEditor.xaml file in three places), it was forcing the default brushes to be Red since null's weren't being allowed. Before you launch that sample, please add IsNullAllowed="True" to each of the three BrushEditBox instances in that file so that it works as intended. We are making that fix for the next version.
There is also documentation on highlighting styles and highlighting style registries that tells you how to update styles.