I see how that may help for you and possibly others, but it won’t stop the complaints entirely. I can almost guarantee you that conversations like this will happen:
user: My account was suspended, I want to reactivate it now!
we: You can reactivate the account temporary so you can download backups. But you can only do it once.
user: I clicked the reactivation button but my account was suspended again 20 minutes later! Your servers are broken!
we: Yes, it’s a temporary suspension. You still need to wait for the full reactivation.
[later]
user: My account is suspended again! I want to move away from here, give me my data now!
we: Sure, you can use the temporary reactivation on an account to get access to the data so you can back it up.
user: But it says “you cannot use the temporary reactivation because it’s already reactivated before”! Why can’t I reactivate my account?
we: Because you already used the backup option, but you didn’t use it for backups when you should.
user: You are a bunch of scammers! I will give you a 1 star review everywhere! Buhuhuh!
Systems which are clear help to prevent situations like this. And systems which are simple tend to be clear. So “if you hit the limit, your account is suspended for 24 hours” is a lot easier to explain than if there is a temporary once off exception which can be used at some times.
Also, there are a lot of topics about the resource limit suspensions. But in my experience the main requests are “I want my website to be back up right now” and “I want to know exactly what to do to prevent this from happening again”. A temporary reactivation solves neither of those issues.
And if I had to build it, a “suspension light” is probably easier to do that a “temporary unsuspension but only once”. But I don’t have the means to build something like that.