Not true.
AWS migrates live instances to new CPUs without needing to stop or reboot the guest.
When a migration is needed, the hypervisor begins copying blocks of memory to the new system, keeping track of what blocks are written inside the guest during the migration. Once enough has been copied, it hibernates the guest, copies the remaining memory, then wakes it in the new system. On a system that isn't writing to large swaths of memory, it can take only a few milliseconds. To the guest, it might appear that the CPU froze for a tiny bit of time, which could easily just look like a neighbor got noisy.
Yes, but that's irrelevant here because the CPUID report won't change across live migrations.
Consider what would happen if you were live migrated from a machine with AVX512 to one without. Your app would suddenly start crashing with SIGILL for no apparent reason. So, live migrations always preserve the apparent CPU feature set. If you started on a machine without AVX512 then until the VM is rebooted you will remain on such a (virtual) machine.