Guys, I’m typing this with my fingers crossed… 
but the 2025-03-05 stable update’s kernel (6.12.12-2 → 6.12.17-1) and/or firmware (20250109.7673dffd-1 → 20250210.5bc5868b-1) seem to have fixed this bug!
I almost can’t believe it, it’s been so long since kernel 6.1 came out and at every stable update I tried running a 6.1+ kernel only to have to go back to 5.15, but after this one and 15 days of uptime running 6.12.17 things are looking good.
Very happy, as due to this bug I was planning to get a new laptop this spring, while for the rest this one is still serving me well.
I’ll wait a few more days just in case then I’ll update the kernel.org ticket.