I don't believe there are rules fo thumb or general reccomendation for this decision.
You will find on https://documentation.commvault.com/commvault/v11/article?p=30807.htm reccommendations to live browse disks larger than 16TB what indicates that the live browse can cater for most of the 'typical' disk sizes in use.
Before switwing from VMware live browse to windows file system agent, you could enable the "Collect File Details" option on the "Backup Options" tab. It is the same as 'Enable Granular Recovery' in previous Commvault versions. The downside is that the backup may take longer. I honestly tested thisoption in several customer and could not observe any negative impact.
Something elso to be explored is improving the live browse performance, you may improve the live browse performance by changing the job results path to a faster (SSD preferabily disk). This folder is utilised by commmvault to download and access the extents for the disks to be browsed.
Another consideration is how often you restore granular files. If it is quite often, the agent could ofter a better restore experience not only considering the live browse decision, for instance the 'find' funcion for files under file system agent works in a much more compreehnsive way than in a live browse restore.
In summary I would enable "Collect File Details" option, check the backup permance and data reduction efficience and test the browse and restore. If it suites your required... That's the way to go :)
Please note that I based my response on VMware VMs and Windows File System agent assuming the most typical scenario :).