And thats before we take into account the custom chipset that the Amiga has, which allows the OS to offload tasks from the CPU. Not only is the OS different, but the hardware is completely different. The PC OS expects the CPU to do everything,
The statement "PC OS expects the CPU to do everything" is wrong.
For example, refer to cache coherent DMA issues with AmigaOS 3.x/Classic Amiga HW, AmigaOS 4.0/A1 HW vs modern PC HW/mainstream OS.
Unlike AmigaOS3.x/4.x, both Linux X86 and Windows expects the hardware to do cache coherent DMA functions transparently.
AMD K8’s integrated Northbridge can speculatively pre-fetch data without OS or CPU’s intervention. This is also true for nVidia’s nForce 2 Northbridge (for K7).
AMD's hypertransport links operates transparently in X86 OSes without specific hypertransport support.
In "pure" DX8 and DX9 PC HW, Vextex and Pixel Shaders are programs for GpGPU. CPU may intervene for JIT shader re-compile. Think of it like a JIT SIMD/MIMD re-complier for GPU’s SIMD/MIMD shader engine i.e. for maximizing specific GpGPU features and frame rates.
We all know the results of CPU driven DX 3D 7/8/9 Reference Render vs DX 3D 7/8/9 HW render in regards to frame rates.
AmigaDOS doesn't. Ok, so the PC has GPUs... these didnt really come of age until, say the advent of the Nvidia G-Force Yes, I know there have been grpahics accelerators for the PC since the 80s, but these really relied on optimised CPU drivers.
They are not CPU drivers. In basic Windows API accelerators, line draws is offloaded to 2D accelerators.
One could argue that is still the case, as a driver is still needed for the latest video card or physics processor,
Gfx's driver maps to Windows API.