I am not sure I understand your question fully.
If you mean: why do you have to create a xaml resource to apply a style to a cell?
... that bothered me too, while I'm coming from Win Forms where you can access anything at design or runtime, Xaml initially felt like a step backwards and counter intuitive.
I too wanted to write something in c# like:
Style x = new Style();
I think its because the Xaml elements have to be registered before runtime, you can then manipulate them, share them and swap them round during runtime, but they must be there to compile the Xaml, which is necessarily "Fixed" when you F5.
does that make sense?
I guess as a transition/translation between two quite different architectures there has to be some compromise, and the beauty of Xaml - as I'm finally beginning to see - is that its small, neat, efficient and static and transferable.
I'm a home/hobby developer, so all the above might be wrong! But, I am starting to get really exciting results with c#/xaml mix, and what seems weird to begin with eventually does make a lot of sense, and actually helps the structure and discipline of your