Looking at this article while trying to troubleshoot horrible long distance vmotion performance:
How to tune Long Distance vMotion bandwidth for better performance (for hot data)?
All changes to vsi are ephemeral (don't survive reboot) and usually active immediately, the two you mention definitely are. Please use the advanced setting for the first option instead (and reboot), to set the 2nd at every boot, you can use local.sh (up to 6.7): https://kb.vmware.com/s/article/2043564
We usually don't recommend using vsi(sh) as it is not a (customer) supported interface, let me update the KB to use the advanced option for the first setting and check whether we handle the 2nd one differently in more recent releases.