At the end of the day, if you're a developer, you don't get to call the shots in terms of what issues get fixed when.
That's up to the lead dev/product owner/BA.
You can flag issues and propose solutions, sure.
If you think the company isn't worth the trouble then quit and get another job, there are plenty of tech opportunities out there, one's that are no doubt more dev focused.
The trick with burnout is to learn how to bs. You're going to miss deadlines and there will always be too much work. The trick is no one knows exactly what you are doing 100% of time. If people ask tell them just say 'yeah, plowing away just got to finish off a couple of bits and I'll get back to you'.
At the end of the day, if you're a developer, you don't get to call the shots in terms of what issues get fixed when.
That's up to the lead dev/product owner/BA.
You can flag issues and propose solutions, sure.
If you think the company isn't worth the trouble then quit and get another job, there are plenty of tech opportunities out there, one's that are no doubt more dev focused.