Before writing my own copylefting license for my upcoming software company, this license permits the full copylefting requirements, both to my contributors' sources and the piece of text itself, but what to do which I am unsure if this license is FULLY or SEMI GNU compatible and approved?

From what I read over the years, it is very highly recommended if at all possible to use one of the existing copyleft-compatible licenses. The Open Source Initiative also maintains a list of properly vetted licenses, including reciprocal licenses (e.g. GPLv3) and non-reciprocal (e.g. ISC) and anything in between. License proliferation is one of the many problems that avoids. Having forgotten something or having unintended consequences are also common problems when people roll their own.

Can I ask what specific goals you have for licensing? It is quite likely that we can find one of the established licenses that fulfills your goals.

And I very-frankly suggest that it's time for your "upcoming software company" to select and put on retainer a local, qualified attorney.

You might not know why you need an attorney – until you do. And then, it's really too late. An attorney is simply a subject-matter expert in the law, and is usually a specialist in one aspect of law or another. If you are preparing a copyright (or copyleft) license, you really do(!) need to pay for the services of someone who "truly knows."

Attorney's fees are a fully-deductible business expense on your corporate or personal (if an LLC) taxes ... and, trust me on this, damn well worth it.

So: find a nice lawyer, dig a hole twenty feet deep, and bury him or her. Because, "deep down, attorneys are nice people."

Honestly, my copyleft license is applied to my my own packages repositories prohibiting against the blobs and every packages (for myself and my rolling and LTS contributors) are re-licensed under my copyleft contract which I need to start writing it.
This copyleft license also needs to be applied to my own Git services which I also need the every Git contents (for myself and my Qt applications contributors) to be also completely free software.
Within this copylefting license I will also use my deblob tools like freed-ora-freedom and freed-ebian from FSFLA mirrors, as to enforce free software for both my every operating systems and my Git services.
Here, I think my last step needs to be the legal advices, right?

What aspects of blobs are you trying to avoid? I would think that the GPLv3 or AGPLv3 would have you covered in that regard.

Here, I just need to defend against Unix-like based blobs, and I have a tool like freed-ora-freedom, your-freedom (Parabola), kernel-libre to deblob, but of course I have tolerance to m$-based blobs which you need Wine and the derivatives and RUNNING THEM IS NEVER RECOMMENDED TO ROOT, also PlayOnLinux and PlayOnMac denies to run it as root but q4wine NOT YET denies but I will tweak it to deny root to run it.