After digging into it some more, I'm finding it to be a combination of neat things and annoying things. Some of the annoying things have been caused by me being new to the technology, but some others just seem to be annoying things.
It doesn't seem to be hooked into the refactoring capabilities of Visual Studio. If I change the name of something using Refactor, it isn't changing the references in the XAML. And I created a WPF control in a class library and included it another project; whenever I change the control, I have to close the solution and reopen it to get the changes to register in the other project, which is annoying - although that might have something to do with the fact that I'm trying to use WPF controls in Forms. Or maybe it's because I'm using Resources wrong, I'm not sure. It also seems to be sensitive to obfuscation, and I have to disable renaming for the stuff that's referenced in the WPF Control (which may be because my obfuscator doesn't do WPF yet, or maybe because I don't know how to configure my obfuscator to properly handle WPF). It also no longer works if I try to link all the DLLs into a single DLL during obfuscation - my program can no longer find the WPF control when I do that.
All in all, it looks like it can do some neat stuff, but it looks like it involves another learning curve. I think I might put it off for a while, and maybe look at it again later.