Given your options, I prefer renaming the current "No" to something else, and the new "No" move from cache to array just like yes does.
What I really think needs to happen is a total redesign of the cache pool settings.
Divorce the two concepts of file placement and mover action, like this.
Each user share can define both initial and final file location.
New files destination (array, cache pool 1, cache pool 2, etc)
Mover destination (leave in place, array, cache pool 1, cache pool 2, etc)
That way when somebody updates a share allocation and runs the mover, it's obvious what should happen.
Bonus points for conditional mover behaviour based on age or space thresholds.
Extra special bonus points for second conditional destination, i.e. move files to cache pool 2, move files already in cache pool 2 older than 1 week to array.