Not as far as I know.
Even if you manually fstrim, it does not return the capacity above that level, and it is configured in CentOS so that vSAN can automatically unmap / trim.
In fact, I tested creating/deleting files to check that the vSAN Unmap/Trim function works properly in that VM, and I could see that the capacity increased and decreased.
So, as a last resort, I cloned that VM and checked the capacity, and as a result, I was able to see that the capacity was reduced to about 130 GB.