The game is not *crashing*, it is intentionally and cleanly closing itself. I edited the config to disable Steam and removed the steam error from my log. If you open it with no other windows open, you will see it reach the title screen menu for a few seconds before closing. There is some sort of alternative copy protection in place that is causing it to close - the developer probably used a different method than the one the previous 'copy protection fix' patch resolved. I am too busy to hunt it down, but that's what it's doing (and where it's doing it: immediately after the game displays the main menu for the first time)
King B is clearly willing to expend some effort to ensure that his Patreon early releases are in fact an early release that is hard to pirate, and given that he only provides them one week in advance that makes it improbable that the community will reliably hunt down and remove whatever method he's using in each release before the clean one comes out.
The people whom it is working for have something different than those it does not - perhaps they were at one point Patreon supporters of King B and previous installations left something behind that the game is checking for and assuming they are still current subscribers (or maybe they are). Somewhere right after the game pulls the main menu screen, it has an If statement that is checking for something and when it isn't present it is doing a clean return, which ends ren.py.