Deleting Config Page doesn't clean up custom field permissions

I was deleting an older config page that wasn't necessary anymore and I noticed when trying to save an unrelated entity, I got an error related to orphaned permissions on fields that no longer exist because the config page was deleted.

I ended up editing the config files that had these orphan permissions - they were user.role.rolename files. I also found a single token to remove as well, during this process.

This exercise was actually useful to see where deleting the config page might have inadvertently impacted something else. So, if a fix were to be implemented, I think it should list what would change. Since deleting a config page that was in use with custom field permissions is unusual, stumbling upon this post will probably be sufficient.