Filesystems generally don't replay the journal to memory, but instead replay it to disk as part of going read-write. Conventional replay of the journal would make these issues even worse.
But it's worse than this and the above doesn't solve the problems. Say you've mounted already, the filesystem is changing under you, and assume no cache for simplicity (caching makes this even worse):
For instance, say update A truncates a file and frees up some storage. update B allocates this free space to another file. Update C writes to it.
A different system starts a read, and finds the metadata for the first file. Then it hesitates, and later reads the data from update C in the wrong file.
Most filesystems are not written with this use case in mind-- mount readonly while someone else updates. It's something that I've tried doing with varying degrees of success in the past (sometimes perfect, sometimes with strangeness at the application level, sometimes with kernel panics).
Pretty much every modern file system is tolerant to computer crashes via journaling. Mounting an in-use FS as read only is effectively the same as mounting a file system after a computer crash. Not self consistent, but close enough it can be repaired in memory (i.e. without touching the disk) via replaying the journal.