Hi rattylaa,
For one of our Customers, we had a similar scenario, where they didn't use any of the OOB security roles, except the System Administrator (of course) and System Customizer. They had their own Customer Service role and Sales/Marketing roles
inspite of CRM having them OOB. So, what we did was created roles having names as "CustomerName - SecurityRoleName". This way, we insisted they keep the OOB roles and use the ones starting with "CustomerName - ...". That way they didn't mixup the OOB and custom
rules and they agreed to it.
If that is the case with you, where they suspect mixing up custom roles with OOB ones, you can suggest what we did for our case. Or else, if they are too sceptical to use the OOB ones, you can remove them from Dynamics CRM (unless you already have users
assigned to these rules). I believe they would only want to remove the OOB ones because they don't want to use it, which means they wouldn't want to create one by copying it from existing OOB ones as well; which means you can go ahead and remove them.
Admin QuikView Solution for CRM 2013