So any drop in productivity must be accompanied by a plausible and pitiable excuse. Like "I can't sleep that well after that car accident" or something similar (but never "I'm burnt out" or "I stopped giving a fuck").
My opinion is that the company likes having OP in a desperate state because in doing so he won't have enough time to look for a job elsewhere.
Some pitable excuse would just paint target on OP's back. Burnout is normal in companies with high churn, they have process to cul weak members... And OP does not have any holidays or health benefits, tough sh*t..
The whole point is to fly under radar, until OP finds new job. Detaching from company politics, staying invisible. Some excuses and more communication push you deeper, in oposite direction.
Also company probably has no real way to measure productivity. People who understands code base left long time ago. Managers are just paper pushers. The only information management has is from OP. Some excuses would be admission of slow down.
Ideally this productivity drop would be spred over several weeks, maybe after major holiday, reorganization or reassignment.
Wasn't just me at this workplace, but all the individual contributors were as well. We saw the writing on the wall, that the co-founders were not interested in full-time conversions and turnover rate increased.
It actually made me question the legitimacy of software careers for a while, because I was caught in this illicit operation.
There is no point to negotiate, or to sue them.
Start job seeking ASAP. Do not quit, but work less hard. Insert delays into your responses. Before you commit code, take 30 minutes to study some subject or seek job.
Drop productivity, but no engagement (that is metric that matters). Still answer client calls at 4 am, pretend you work 12 hours a day etc... They will shout at you for a while, but after couple of sprints, requirements will adjust and be less demanding.