Everybody agreed that "Leap seconds" are a sufficiently bad idea

No. Not everybody. I prefer accurate time, and all the complaints I've heard hold little water.

My servers need to timesync forwards and back all the time, eg timedrift. They need to jump to new times, or slowly drift, depending.

VMs can be hypervisor starved, or need to move to a new host.

Servers also need to handle missing time. Any daemon or program which cannot handle this is buggy, broken, and needs to deal.

Leap seconds are just part of all of this, and present no new issues compared to normal time change. I question the capabilities of any engineer who singles out time second as difficult to deal with, time is constantly changing on servers. Constantly.

So back to the start, no... everybody doesn't agree. Google isn't "everybody".