Those are two fundamentally different jobs. Except in the scenario that the UX design is for a product the primary purpose of which is OOP development (e.g. an IDE).
Otherwise, of course, there is no harm to knowing the "principles" of OOP. Further, knowing about a broad range of different things (including OOP) can certainly help you to think differently. But it is equally important to understand that OOP is just one of many approaches to programming, there are others (e.g. functional programming). But to get to a level where your skills are actually useful in a production environment, you need a lot of practice/experience as a programmer.
On the other hand, there are designers, who out of their own personal interest, learn programming and get good at it. But that's the same as a marketeer learning programming and getting good at it.
This is a fantasy that some hiring managers and many recruiters tend to have - that they need to hire genius all-rounders for all jobs. Usually, it reflects a lack of understanding of the role they themselves are hiring for.
The only (rare) situations where it is useful is in extremely small product teams and barebones startups. Even then, it is far more practical to have a programmer who can do some basic design work, than the other way round (designer moonlighting as programmer). It is easier to have a programmer do a crash course on design and get them to do some basic design work, but a crash course in programming won't make your skills actually useful for anything other than building simplistic toys/prototypes.
"Developers would immediately get the gist of the screens."
That is not the job of the designer. Products are designed so that the users, not the developers, immediately get the gist of things. The designers' customer is the user, not the developer.
As a practical example, consider Jony Ive, the legendary ux/ui designer. It is easy to check that he is in no way a qualified developer. One can assume that degree courses in industrial design are meant to prepare people to work as designers. It is easy to check if the curricula of some of these courses include any real OOP/programming content (they don't).
Here is a quote from Don Norman, the guy who invented the term ux
I invented the term because I thought human interface and usability
were extremely good. I wanted to cover all aspects of the person's
experience with the system including industrial design graphics, the
interface, the physical interaction and the manual. Since then the
term has spread widely, so much so that it is starting to gain its