I can't see much of a reason to even support such an old processor at this point.
There are many, many reasons for maintaining support for alternate architectures. How many problems would be baked in if we always had this attitude?
Back in the day when "all the world is an i386", people complained when told about how their code has bugs when compiled on 64 bit processors. Imagine if we had baked in all of those 32-bit-centric bugs that broke compiling on 64 bit.
People do the same thing now when told their code doesn't compile cleanly on 32 bit, on PowerPC, on ARM, on big endian, et cetera. Imagine if we now acted like "all the world is an amd64", and lots of code was simply broken on aarch64?
If you were alive and paid attention through other transitions, you'd understand how every example of programmers being "forced" to care about the correctness and portability of their code has paid dividends years later.
Though I wasn't making a definitive statement on which category m68k belongs to in the first place.
If anyone wants a further back in an even earlier day example, see http://www.catb.org/jargon/html/V/vaxocentrism.html
I would very much like to learn how to get one 1) running on an FPGA 2) running Linux and then 3) set it up to automatically run new builds.
[1] https://silvaco.com/design-ip/embedded-processors/ [2] https://www.farnell.com/datasheets/1703092.pdf
As far as I'm aware, there are no longer any "true" 680x0 parts in production. NXP stopped production of the 68SEC000 in 2014; anything still in stock is at least that old.
I also read somewhere that the 2011 earthquake+tsunami destroyed the only fab that had still been producing the original (well, CMOS) 68K-family chips, and Freescale had been planning to close that fab anyway.