For those on your Community in the Cloud platform, the public status service is a step in the right direction. I'm sorry to hear there have been such significant problems and launching it is likely the result of an onslaught of inbound support chat requests that the world is on fire for them.
It would be great to take that reactionary energy and channel it into useful proactive solutions by being equally transparent with the status of known bugs/issues (and workarounds if applicable) and the expected resolution availabilities beyond "some future version."
Your list of issues is welcome, however formalizing this along with "available next maintenance release," "next minor release," "next major release," "4.6.3.1," etc. would be greatly appreciated. I have no idea when the PHP8 error will be made available that the team worked hard to fix this week.
I know you probably don't know either right away, and that it takes a bit of discipline, yet so does maintaining a status page.