A
Wickie/Vicky moment: a status message ticker!
Given the space restrictions that's a tough thing when cost-benefit ratio is important (it is - mostly/always).
Fact: we only have the time and space (for message display) domain.
Leaving the principle of displaying only one message (after another) unchanged would require introducing a combination of status message categories/priorities to decide what is to prompt for a given interval. From my own experiences, that's begging for troubles. Everything screams for customization: the categories, the interval length etc.; finally, somebody (me) asks for an option to change all of them temporarily in scripts.
And after all you end up with a fast sequence of equally prioritized messages - and it starts all over again.
Either a plain history with a simple access, or a smarter approach indicating message bursts on the UI.
Of course, the latter again rests upon the time domain as a burst is defined by a frequency threshold. The indicator, for example, could be a simple char (suffix "*"), an (overlay) icon or change of text color. All of them could render the status message icon a clickable button that opens the (recent) status message history.
My favorite is a dynamically resizing status message area (a line-limited popup expanding upwards) which consecutively shows all messages triggered within a given time (a FIFO queue with a display for the last x entries))