Description of problem:

After freshly installing a RHEL9 minimal system (so, with runtime journal only and standard journal settings) and setting the loglevel to debug ("systemd.log_level=debug"), I see multiple times the following messages on the console:
-------- 8< ---------------- 8< ---------------- 8< ---------------- 8< --------
[ 59.714076] systemd-journald[697]: Data hash table of /run/log/journal/6e07b59bccc94c8bb84abf4f95c9cbda/system.journal has a fill level at 75.0 (6049 of 8064 items, 4644864 file size, 767 bytes per hash table item), suggesting rotation.
[ 59.717640] systemd-journald[697]: /run/log/journal/6e07b59bccc94c8bb84abf4f95c9cbda/system.journal: Journal header limits reached or header out-of-date, rotating.
-------- 8< ---------------- 8< ---------------- 8< ---------------- 8< --------

Stracing systemd early during the boot, it appears that *systemd-journald is supposed to log this at INFO level but never send this to the console.
I can see however the following trace, showing it's sending to /dev/kmsg:
-------- 8< ---------------- 8< ---------------- 8< ---------------- 8< --------
697 15:31:53.315917 writev(6</dev/kmsg<char 1:11>>, [

{iov_base="<46>", iov_len=4}, {iov_base="systemd-journald", iov_len=16}, {iov_base="[697]: ", iov_len=7}, {iov_base="Data hash table of /run/log/journal/6e07b59bccc94c8bb84abf4f95c9cbda/system.journal has a fill level at 75.0 (6049 of 8064 items"..., iov_len=201}, {iov_base="\n", iov_len=1}], 5 <unfinished ...>
:
697 15:31:55.051198 writev(6</dev/kmsg<char 1:11>>, [{iov_base="<46>", iov_len=4}

,

{iov_base="systemd-journald", iov_len=16}

,

{iov_base="[697]: ", iov_len=7}

,

{iov_base="Data hash table of /run/log/journal/6e07b59bccc94c8bb84abf4f95c9cbda/system.journal has a fill level at 75.0 (6049 of 8064 items"..., iov_len=201}

,

{iov_base="\n", iov_len=1}

], 5) = 229 <0.002330>
-------- 8< ---------------- 8< ---------------- 8< ---------------- 8< --------

Version-Release number of selected component (if applicable):

systemd-250-12.el9_1.1.x86_64

How reproducible:

Always

Steps to Reproduce:
1. Boot with "systemd.log_level=debug"

Actual results:

Message on console

Expected results:

No such message on console