I don’t know about the general perspective but I can give you mine (since you asked 
)
I would advice against making trivial setters and getters.
If you need some additional work done when setting or you need to cache the answer when getting, please do use them but name them appropriately. (in which case they stop being just setters and getters)
In Blueprints I use protected functions and variables only to prevent clutter of the right click menu but in that case I don’t expose them at all. I often have multiple public events calling the same protected function with different parameters.
Anyway this is a discussion by people much smarter than me: c# - Are accessors (get and set functions) popular with C++ programmers? - Stack Overflow