Using procs for CUD operations is fragile. It comes down to the fact that you're not mapping entities onto tables/views but entities onto proc signatures.
The read operations are actually quite easy: use projections
You've to save the entities manually through the procs, passing field values to parameters, there's no facility built in for this. You could try to do this transparently: in overrides of CreateInsert/Update/Delete query methods of adapter.
There, you'll use the target table / view as key in a list with procs you've made, so you can then create an ActionQuery object with the proc call and all parameters set. Then you return that one and everything goes as planned.
Be aware, it's fragile: there's no support for when your entity changes or your proc changes, so it then could break at runtime.