When saving tracks that have duplicates could the application save the highest bit-rate and/or largest / longest track first then incrementing the rest as it does now?
This will first require Picard being able to detect and handle duplicate files. This is on the wishlist already. I only found this ticket, but it basically is about this:
What to do in case of duplicates and which files to prefer must be configurable as this is highly dependent on personal preferences.