I've been using Intel hardware on Linux for more than 10 years. The instances of driver issues that I can think of are very very few and they were never related to anything Intel did.
I wonder what hardware you've been buying. I've tried Apple, Dell, HP, Lenovo, Intel OEM, Toshiba, ASRock, and a half dozen others. I never saw any of them run Windows (OEM or from Microsoft), Linux, or MacOS X (on the Mac) reliably.
The most recent Intel machine that did work reliably is now 15 years old (and humming along nicely, for what it's worth).
Sure, they had Linux drivers, but they also would do crap like kernel panic, unsuspend in my laptop and overheat, screw up USB, and so on. They did it under all operating systems.
My current desktop is an AMD system on chip. It's great, except it has an Intel WiFi/Bluetooth module. There's been a bug open against all Intel Bluetooth modules for about a decade:
They fail to advertise themselves in a timely fashion at boot, so the intel driver (Linux or Windows) doesn't see them so you have to keep rebooting until it does (or write a bash script that retries modprobe).
Here's the manual for the wildly popular ASUS bluetooth dongle that works around this crap by not using an Intel part. Look at page 1 where they show you how to disable the Windows driver for your existing Bluetooth radio, which apparently can't coexist with a second bluetooth adapter under windows:
The most important pieces, IMO: Asus or Gigabyte motherboards, integrated video (because GPU drivers are usually unstable), Intel Ethernet (avoid realtek), Intel K series unlocked processors - not overclocked, if anything I run them underclocked for cool, quiet and efficient operation. And use quality RAM, that's pretty important. Debian Stable.
