It isn't clear to me that this is a CPU "bug" so much as an exploitable design-deficiency which given the complexity of modern microprocessors is inevitable. Certainly still bad for Intel, but they aren't the only modern microprocessor affected (ARM64 is too) because the exploit subverts fundamental behaviour of virtual-memory management. I wouldn't overreact and abandon Intel over this given the information to hand.
The performance cost for Kernel Page Table Isolation is to make calling into the kernel more expensive but most GUI applications, like games, perform their work in user-land and call the kernel relatively infrequently.
If everyone's favourite Linux gaming advocate is to be believed the
KPTI changes on Linux do not affect games performance which is a better indication of the affect on typical end-user software. The synthetic tests will be absolutely clobbering the I/O and other subsystems which isn’t how GUI applications usually work. Servers, databases etc. do those sorts of things and that is presumably why the kernel maintainers have jumped on this with such gusto.
On Mac it might affect high-end video/audio/etc workflow, but only if FCPX (or whatever is used) makes a *lot* more system calls than your typical game and I'm sceptical of that.