They enable your option 2 and allow the implementation to change behind the public API. Should theta/R have getters is entirely up to your API decisions.

The point of getters and setters is they're the bare minimum of encapsulation. The advice is to ensure even reading a field should be abstracted so implementation details do not cause large reactors of downstream code.

How this is conflated with 'every field should have getters and setters' like it is in this discussion I do not know but that is not the intention.