In the past, specifically when running SolidWorks95 (yes, long time ago), it would crash with AMD CPU and the reply was that the AMD was not 100% binary compatible with Intel. Never touched AMD again since then.
The limitation is simply this: if you run the software with non-certified hardware and it crashes, you don't get support, because the crash is considered to come from non-certified hardware.
Also, consider that in certain industries it is mandatory to use certified hardware, specific driver versions, etc., so that there is a chain of liability if things go wrong. Imagine you determine through FEA simulation what thickness an aeronautic component need to be. The component then fails. Did you do something wrong in the CAE software? Is there a bug in the CAE software? Is there a bug in any driver? Is there a bug in the floating point unit of the CPU?
So what you do is to only use certified hardware and drivers, allowing to exclude these when things go wrong. Also, the software manufacturer can hardly test his software with all possible hardware and driver combinations.
Anyway, I would love to live in the parallel Universe where Intel fixed its problems and launched the Core i9-15900KF without any planned obsolescence or manufacturing defect...
And yes, my computer being a company computer, if I get to a point where working on the PC gets annoying, I will purchase a new Core i9-14900KF and send the old i9-13900KF to RMA. When it gets back, I keep it as a spare. Right now, the only things I noticed is that with one simulation software, the process would be terminated (can't remember the error code in Event Viewer). This was repeatable. When I redefined BIOS settings according to instructions (and later through BIOS update), these crashes stopped happening (same project now simulated correctly to the end). Note that only the simulation software crashed. All other processes and Windows continued to work fine.
Yesterday I had two non-reproducible crashes of a different software, with the same error code. This software uses the CPU to 100% for like 10 minutes and I think this is what randomly crashes this application. Perhaps further limiting the BIOS would fix this, too, but I did not have the willpower to reboot into BIOS and randomly test settings...
I will wait for the mid august BIOS update and then decide what to do.