When extending the size, as it involves deleting the partition, you will have to recreate it again at whatever number it starts.
otherwise it won't be recognized at best, and at worst there can be data corruption.
If that VPS is a template for creating other VMs, I would take the trouble to recreate/move the beginning *and * the data/sectors to sector 2048.
As it is a VM, if you do want to move the partition, I would not exactly move it, I would create a partition on the side, copy the data and boot with the copy partition. That is the beauty of working with virtual machines, you have more room to test things.
PS. As for my strictly personal opinion, the small gain on performance does not make it worth moving it from sector 63. I would wait for the machine to become retired, it will happen sooner or later.
As for partitions alignment:
You want to leave the partition aligned to the 4096 byte boundary. On that way real sectors are mostly certain to be aligned with virtual sectors and VMWare will your hypervisor/VM will extract a better performance from the hardware.
For understanding why unaligned partitions are a performance problem, see this image from purestorage.com:
Consulting the white papers of a storage specialist in the industry to have a better idea what are the current best pratices:
Modern vendor-supported operating systems (OS) from Microsoft and
Linux distributors such as Red Hat no longer require adjustments to
align the file system partition with the blocks of the underlying
storage system in a virtual environment.
(.e.g. "leave the default settings alone")
However to continue replying to the original question, visiting a couple of linked white papers:
Aligning your partitions to a 4K boundary in both the VMDK and the LUN
is a recommended best practice
In the output for each device, multiply the start by sector size
(normally 512 in the fdisk output), and then divide it by 4096. If the
result is an integer (whole number), it is ALIGNED, if not, it is
So, checking your question about creating a partition at sector 63:
512 * 63 / 4096 = 7.875 => MISALIGNED
I would probably use and leave the default in the future at 2048. Let's check it:
512 * 2048 / 4096 = 156 => ALIGNED
FAQ: Guest VM file system partition/disk alignment for VMware vSphere, other virtual environments, and NetApp storage systems
How to correct guest VM data partition alignment in a VMware vSphere 5.x environment
How to align blocks in VMWare ESX