Model-View-ViewModel is a UI separation pattern. It does not specifically address the role of services in your application. But in general, your "Model" will likely have persistence needs that will need to cross out of the UI layer into a service layer and WCF provides a good transport for that.
Using a dependency injection framework (which is common in MVVM) you can register your WCF service interfaces with the container so that you can work with interfaces instead of directly with the WCF client proxies.
With regard to WCF data services vs. RIA services, I don't know the jury is still out on that. WCF data services is released, RIA services is not. RIA does tend to blur the lines between what is client and what is server. This can be both good and bad. It solves a lot of problems with duplicated validation rules and such but I personally get a little nervous about such tight coupling of the client and server.