This is something that does not require a debugger perse. this is something that can be implemented by a "smart" log. beside the log entry there might be a button to see the trace + state at those points. could even allow log() to have an option for this.
But you have to
1. stop the program
2. edit it to add the new log
3. rebuild the program
4. run it
5. get the program to the same state to trigger the log
And then you see the result of what you printed, figure out you need something else as well, and repeat. Instead you can just trigger a breakpoint and inspect the entire program's state.
Have you ever had to "now click on the left... no, up a bit. No go back you were just there. It's the third one from th... I'll just paste the link in chat" when you were standing next to someone's desk? No.
The only benefits of working from home are:
1. No commute.
2. Can do life stuff (we finally have a solution to the dumb problem that shops etc. are only open when people are at work).
3. The company doesn't need to spend money on offices.
The first two are huge bonuses for employees, but the company doesn't give a shit about them. At best they care about paying for offices, but that's pretty minor (especially when they've already paid for them and they're sitting there empty).
Most organizations are so inefficient, that all of this is barely a factor - whether or not work is getting done at 1% of the rate of what it should be getting done, or 1.3% isn't really a dealbreaker for the company.