Evaluate Entire Batch Rename for Conflicts before Rename

What problem do you see this solving?
When using a batch rename with a counter token often the rename will identify conflicts with files that are going to be renamed with a different name. I would like Capture One to implement a feature that evaluates if the naming conflict will exist after the completion of the rename before appending the filename with a "_x"  where "x" is the next number without a naming conflict. This could be done by assigning all files in the batch rename a temporary name before evaluating conflicts.

When was the last time you were affected by this lack of functionality, or specific tool?
The lack of evaluating whether there will be a conflict after the rename happens nearly every time I need to rename files using a counter token because I need to adjust the order of the sequence by either adding a file to the sequence or reverse the entire order of the sequence

Are you using any workarounds or other solutions to achieve your goals in Capture One?
Yes. I can run a batch rename with text and tokens and then run a second rename with find and replace for "_x". However a bug has recently been preventing me from doing this while reversing filenames that requires the program to be restarted.

Are you happy to be contacted further about this suggestion or request?
yes.

In talking with Colleagues using MacOS this may already exist and not have been implement on the PC version