fyi there is already a fedora selinux-policy upstream kmscon module, why wasn't it used? they might need to enable it or you likely can also ask them if you can take it over
https://github.com/fedora-selinux/selinux-policy/blob/rawhide/policy/modules/contrib/kmscon.te

Also, we worked on some fixes for kmscon 9, just created a PR there
fedora-selinux/selinux-policy#2813

@ca-hu I wasn't aware that there was an upstream selinux-policy for kmscon.
Before writing this, I asked how to do that here
https://discussion.fedoraproject.org/t/selinux-configuration-for-kmscon/140141

Do you have an example of the changes required to use the fedora selinux-policy?

Also FYI, I'm reviving the kmscon/libtsm packages for Fedora:
https://bugzilla.redhat.com/show_bug.cgi?id=2373136
https://bugzilla.redhat.com/show_bug.cgi?id=2373128

Do you have an example of the changes required to use the fedora selinux-policy?

If the fedora selinux policy maintainers decide to activate the module, then it likely will come with the distribution and I think you can just drop the selinux stuff here and it will just work.
I think if you want to carry it as independent policy module you likely need to copy it over and maintain it yourself.
Since I am not involved in fedora nor kmscon, maybe you could discuss this with them directly there: fedora-selinux/selinux-policy#2813