Companies like Microsoft with huge marketing departments hate the GPL because they don't like their users to be free. It's part of their business strategy to keep people locked in. That alone should tell you it's probably not for for you. Sadly you seem to have been taken by their bs, though.
> Once you release something under an OSS license, it is OSS- billion dollar companies can't un-open source your code.
With "permissive" licences like MIT, BSD etc, companies absolutely can and do "un-open source" code; there's nothing stopping them doing it.
GPL actually seems to be what you think OSS is: a licence that prevents "un-open sourcing" code.
If you actually care to understand, you need to first understand how copyright works and specifically how it works against the goals of the free software movement. Then you can understand the purpose and mechanism of copyleft, which is used by licences like the GPL and others to achieve the goals of the free software movement.
But the OSS code remains OSS.
So by using a permissive license you enable someone to use your open source software in proprietary software. Now your open source code runs on someone's computer as part of another software but the user cannot get the source code to the software.
The original is of course still open source. But the combined work is not. There is FOSS running on your computer but you cannot modify and recompile it because it's part of a larger software you do not have the source code to. So for this scenario the FOSS license and source code is of no use to you as the user.
Whether you call that unopensourcing is a matter of definition in the end.