I looked into this, and actually, it seems like maybe you can? https://man7.org/linux/man-pages/man5/proc_pid_oom_score_adj...

So, in actuality, I think your assertion just taught us all something, because despite knowing that the OOM killer and that the Magic SysRq key[1] exists, I didn't know you could configure this as an input!

[1]: https://en.wikipedia.org/wiki/Magic_SysRq_key

I always wanted it to target java processes, as they were always the culprit. These days it's python, VSCode, and antigravity.

This. It's always browser running amok. I configured win+k shortcut key to: killall -9 chrome

It's not a panacea, but in my case setting browser.tabs.unloadOnLowMemory in about:config helped a bunch.

Maybe not in kernel, but running the earlyoom daemon will let you do exactly that in userspace.