I’m personally not a fan of using aliases for things like this. It’s weird, though, that LEAP has packages for python 3.9 and 3.10, but not 3.8. Using a venv, or at least installing 3.8 in another location (like /usr/local or /opt), would get all of your libraries out of the system’s way.
I would think that you’d need to install pip modules that are much newer than the current ones installed by LEAP.
Never tried it with an alias. In my early days of python programming, I would change the shebang in the script to the version I wanted to use; now I find that venvs are better suited for me. With that being said, since 3.9 and 3.10 are available in the LEAP repos - this includes core packages like pip - I would give one of those versions a shot.
As an alternative means of solving your problem, look at anaconda python package. (https://www.anaconda.com) . It installs python and runs as a user. Does not affect the system python modules nor does it use them. Different environments can easily be made that will use any prescribed python version as needed and all the related/necessary modules to operate in that python environment. Will install environments at least to 3.10 and other versions below that you might need. Allows operation with pycharm ide in each environment you have set up.
Can be removed just by deleting a user directory. Has gui “conda navigator” if you don’t want to use cli.