I'm having the exact same issue for accounts on my tenant. In my case, deleting an affected O365 account from TB and re-adding it resulted in the fault returning. I took that same account and added it to a separate test machine with a fresh install of TB on it, and got the same fault again.
Ergo - this fault is staying with the affected account(s), and not the device accessing it. The identical TB (Oauth2) config has been used throughout my testing as evidenced by the fact that I can send and receive quite happily on an affected account, and I can see the folders if I set TB to display all folders regardless of subscription.
What I did find is if I added some test accounts from my tenant that hadn't been accessed via IMAP before, that actually worked perfectly well including the subscription functionality. I now have three such accounts which have been working OK for several days now.
So it appears that something has happened that has broken JUST the IMAP subscription functionality, and on accounts that were using IMAP at the time the problem occurred.
Before anyone mentions deprecation of basic auth, the affected accounts were reconfigured to Oauth2 months ago in preparation for that change, and everything worked fine until the other day.
I have tried turning off IMAP on an affected account in Admin Centre, then turning it back on, and that had no effect.