Hi Tony, Fancy meeting here. ;-)
Some list values are unable to be deleted as the system knows that they are in use in a template or a workflow somewhere inside SCSM. If you go to the effort of finding where these are set and set the list value to a different value you will be able to delete
the list value.
The problem with renaming list values is the value will be stored back in the MP that the list value was originally stored in and this can be a default MP that may get overwritten when you upgrade to a new UR.
"SO HOW DO I GET MY LIST VALUES TO NOT BE OVERWRITTEN BY NEW UR's?" I hear you scream.....
Good Question. The key is to save any custom list value in a custom MP. That way when Microsoft release a new UR or even new version (2016) the default list values get replaced, but yours remain in your custom MP.
Here's the catch! - You have ONE chance to do this!
The first time ANYONE in your management group changes or creates a list value it will prompt for an MP to save it to. This is the one and ONLY time that you can make this choice. From there on in, all values will be saved to that MP. So choose wisely.
How do you know what MP a list's custom values are being stored in?
Again, glad you asked. Check out this blog by this awesome and good looking guy. (Really modest too.) ;-)
https://systemcenternoise.wordpress.com/2015/06/30/what-management-pack-in-scsm-contains-my-list-values/
Hope this helps