Are you a believer in the idea “They who have nothing to hide have nothing to fear”? Hint: You shouldn’t be.
And do you know for certain that your sandboxes and VMs don’t simply pass through the CPUID instruction? And if they don’t, do they rotate their fake CPUIDs? And how often does that happen?


Ctrl+C and Ctrl+V for copy and paste come from non-Unix (I’d say Windows itself, but they may have stolen it from elsewhere), and so it makes sense that those two keys have other special meanings under Unix and its descendants.
Specifically, they mean “Stop what you’re doing” and “The next character is to be entered without special meaning” in most shells, the most common programs that run, often as the main program, in/on a terminal.
As such, most terminal emulators in Linux GUIs reserve those keypresses for their Unix-y functions. Most of the good ones move copy and paste to Ctrl+Shift+C and Ctrl+Shift+V instead.
MS-DOS and Windows command prompts also inherit their use of Ctrl+C from Unix, by way of 86-DOS and CP/M, and were in there long before Microsoft adopted Ctrl+C for copy in a GUI, which is where those other Insert-based keybinds you mention came in.
For an example of Unix Ctrl+V, try
echo hello[Ctrl+V][Ctrl+H]worldin a Linux terminal shell and press Enter. You’ll see the command asecho hello^Hworldand when you press Enter, it will displayhellworld, because that embedded Ctrl+H is a backspace.