One can basically see three “subsets”:
- There is python. The “executable”
- There are modules for python. “Libraries”
- There are applications that run on python
The OS has “platform python” that – as said – will remain same until EOL of the distro.
There are alternative python versions (e.g. the 3.11) for user applications.
There are some modules (e.g. numpy) as RPM for each available python version, so that all users do not have to fetch all modules for their own needs (e.g. with pip install --user or venv).
The dnf, nft, iotop, etc are system applications that run with the platform python and hence stick to that version.
Look at Red Hat Enterprise Linux Application Streams Life Cycle - Red Hat Customer Portal
You should see that the Python 3.9 is supported to EOL of EL9, May 2032,
but the Python 3.11 application stream will retire already in May 2026.
If, for example, the package manager (dnf) would be shifted to depend on 3.11 now, then it would have to be shifted to 3.11+x relatively soon. IMHO, such frequent porting would be wasted effort and expose dnf to “novel bugs”. If the package management, firewall, and whatnot of distro are eaten by bugs, then nobody is happy …