Vault reuse

I think if the folders are auto-managed the order is greyed out so it will likely just write to the same one. If you want to reset things, you can create a new vault, change mapping rules to point to it and then let the system revault and it should move all the content the new vault, creating new folders under the 50k limit rule. Eventually, all the old folders and vault will have unreferenced files and can be unmounted. 

I had manually managed vaults a while back and used this process to shift over to a vault with automatic folder creation.

At the end of the day it doesn't matter because the total number of files on disk won't be impacted.  But my obsessive compulsive kicks in and I go back and set the folders to read/write again at the DB level.  As they fill up, they will be set back to read-only again.  It follows the vault folders sequence order.

update FvFolder set readOnly=0;

Doing a new vault frequently leads to cleanup frustration at the end of the revaulting process.  There are a few files that just won't move or prove challenging to clean up.  It is simpler to toggle the read-only switch and let the existing folders auto-fill again.

FYI: Not all hardware is equal.  Use caution upping the limit on poorly performing hardware.  50k is fine in most environments today.