JSON support in Postgres is really not intended to replace - even as a stopgap - what nosql was used for.
I first started working with JSONB columns in Postgres around 2 years ago, I think, and had the same initial impression - the operators are certainly quite alien compared to more typical SQL, and it took me a while to figure out how to do more complex things.
I kept at it though, and now it all feels more natural. I haven't touched Mongo for about 10 years, so it wouldn't be fair of me to compare, but I love the performance and power of JSONB in Postgres. And having all this right alongside regular relational tables in the sr database is fantastic.
I often work with TimescaleDB too, which again just works alongside everything else, in one database - Postgres really is an incredible database!
To be fair, I use mongoDB for 8 years now compared to less that 1 year of psql JSONB, so I can't really answer objectively.
There were some issues, some our fault, some Mongo's, but I think anything will have teething problems at that scale.
Just make sure you don't treat it like a bucket. Use well defined schemas and indexes, like with any DB.
Postgres JSON operators are cryptic and made my head hurt every time I wanted to accomplish something more complex.
To express it differently, if mongo and postgres where identical operationally, I would choose mongo every day. More friendly and fun. But there are so many horror stories that I am still not sure that it is the right choice for a safe production environment.