The application of procedural control in what normally is a radar environment is extremely difficult. Where there are multiple level changes involved and converging/diverging traffic; radar (separated) segregated routes involved getting all the elements correct can be extremely problematic. Some sectorisation is designed around 'radar routes' co-ordination may need be conducted to other sectors if you can't see them... Because they may not be where they should be if you can't see them etc.
Having ground based navaids to use for the establishment of radials etc is an advantage. However, getting controllers who received little more than basic procedural control (if any) to recall what the learnt in training is still very difficult.
To separate procedurally (in horizontal terms), you would have to request position reports from the a/c you have under radar control, as you can't use info derived from radar to separate procedurally, and this would be a bit awkward. So the best solution, as mentioned, would be to use vertical separation.
I would suggest that you can use radar derived information to achieve procedural standards as long as you apply the appropriate radar tolerance against the procedural tolerances. ie achieving a 30RNAV standard can be done with radar without asking the 'radar identified their distance' ie you can see one 10NM from X and the other is 60NM from X, therefore you must have 30RNAV.... Laterally you certainly can use radar to establish an aircraft clear of anothers (procedural tolerances included) route.