Looking over the Linux ecosystem, I would say that Linux itself has far more blame for the lack of native ports than the developers do. Developing for Linux is complicated, requires constant intervention, has frequent compatibility gotchas, has little "best practices" established, among other issues. Games are complicated things - name one native Linux port that works just fine on Fedora 37 when it was built for Ubuntu 16.04. Unless it got recently updated or is only a simple 2D Game, odds are not in your favor.
For an example of this, read Mike Rose about the game Defenders. Linux was 0.8% of sales, but over 50% of technical complaints. Whereas, if they dumped it for a Proton build, the onus is no longer on them for a working Linux build or for compatibility issues on Linux - its way easier to just say YMMV.
Blaming developers for the lack of native games is like the pot calling the kettle black. Until Linux becomes a decent platform to build for, developers aren't interested in rewriting major parts of their games every time the Linux community has a new idea. The lack of native games, I would argue, is more a failure of Linux than a failure of game developers.
Whether we like it or not, this lack of stability in Linux and the ability to just fork every time you don't like something, has led to Win32 becoming the common API for Linux. You build for Windows and Vulkan, and specifically test your game against Proton, and you can run on almost any Linux distribution that supports Proton without banging your head into a wall, or doing frequent patching every year.