Resetting to the way I got it by reimaging the factory OEM image and then booting up to replicate the original out-of-box experience.
You should never defrag an SSD @mimarsinan - I don't see any of these issues it would appear you have an axe to grind or perhaps a fix to sell...
Maybe just return it for replacement like most people do when they get a machine which offers issues nobody else seems to face.
Too many old school nerds/geeks and IT people try to do old school ways of handling new technology. I always teach my IT people to provision and manage new systems - just say no to destructive imaging and "Fat" Images...I think the key here is that he re-imaged the machine before he used it. One of the problems he reported he's seeing on his SP4 as well. Sounds like his OEM Windows 10 image may have some Surface driver problems. I've never felt a need to reimage a machine I just took out of the box before trying it first to see if there were any problems.
Where did you get the factory OEM image? I didn't re-image mine and I'm not seeing these problems. Maybe as was suggested by @hughlle, you could return it and try using the next one without the re-image. As the saying goes, "if it ain't broke...".
What's interesting is that mine NEVER EVER reached 0.4 GHz on idle with no apps running 0% CPU usage whatsoever. It's always on 0.5 GHz even on battery saver mode Heck, it likes to go to 4.0 GHz even on recommended slider. Just did a CPU-Z validation yesterday and yep 4.0 GHz. Intel Core i7 @ 3990.24 MHz - CPU-Z VALIDATOR
From the device itself, of course.
I always image, using a USB drive and Macrium Reflect, any PC I purchase - at the very first power-on, so I have a 100% clean, un-molested image of the system in a pure factory state.