Your log extract is too short. What is logged immediately at the very moment is not necessarily a sufficient indicator for the issue. Even if it is related or logs an error, it can still just be a symptom that doesn’t tell you the origin. We need data of the whole occurrence, and more technical context. Also, if SELinux causes the issue the way you describe it, there is most likely a denial at some time that affects the issue, even if it is maybe not logged at the very second of the issue.
Therefore, I suggest to make a dedicated boot to create data: boot, log into your account, and then provoke the issue by creating a swtpm VM. After you did provoke the fail, wait 15 seconds. Then go to a terminal and get the output of the following, and provide the full output of both commands:
Feel free to further anonymize the log entries of the journalctl if you want (e.g., MAC addresses or so).
You can create files with the very content by adding > filename.txt to each of the above commands.
Please provide either links to the files, or put the content into code boxes, which you can create by adding a line containing only ``` before and after the output. Alternatively, you can select the whole outputs and select the button </> . In both cases, you can verify the code box in the preview.
I am interested also if / how the outputs compare to the issue of @ultranium1 .