The LGPL does allow for the library portion to be GPL while the rest of the app doesn't have to be, but that isn't the license used in this case. Typically the LGPL favours more widespread adoption, while the GPL favours freedom at the cost of some adoption.
LLVM also has a JIT and a far more permissive license, making it more attractive to those not using a GPL compatible license.
Not to mention LLVM's JIT is far more mature. If you're reading this on Safari then LLVM is JITing for you right now:
You've always been able to distribute a distro that includes gcc and also includes gpl-incompatible programs (like flash player, or apache-licensed programs).
What has to be GPL is the application that you combine the gcc code with, either when you link in the new libgccjit, or in your python code that imports the python module that links to libgccjit, or if you modify/extend the code for gcc itself (or other GPL codebases).
If you decide to write an interpreter for an existing language, and run existing programs on it, then those existing programs "probably" do not have to be under the GPL, for definitions of "probably" that Legal will not be happy about.
If you write an interpreter for a made-up language and then write programs in that language as part of a thinly-veiled scheme to do an end-run around the GPL, then that "probably" violates the GPL.
There is currently no bright-line rule separating those cases; this is something IP lawyers argue about themselves and reach wildly different conclusions.
GCC and related projects usually have license clauses to explicitly confirm this, for example https://www.gnu.org/licenses/gcc-exception-faq.html