Clean up SafeProcessMap

### What

The current `SafeProcessMap` is very confusing to read.

* method names are lying.
* e.g. search is actually a replace.
* there are docs strings that explain the internal logic instead of the outcome, making it brittle (it seems this is already outdated?)
* we return enums/ints and modify an out parameter instead of using results.

### Acceptance Criteria (DoD)

* Method names correctly describe what they do.
* Doc strings match what methods do without over-explaining.
* Think about using types that would guarantee a user has to do error checking.

### How

_No response_