Doing this would require resolution (knowing the structure of your supertype, which requires analysing that source file, etc). This results in chicken and egg issues: If lombok lets the compilation process advance that far, it's too late to add getters and setters and such, but if we don't, we don't know what the parent class has.
There are solutions to this (val and @Delegate and @ExtensionMethod employ them), but the number of bugs, subtleties, and performance issues that those features entail is already a fairly heavy support load for us at the moment. Until we get a lot better at doing resolution properly and quickly, @Data and friends will not be using resolution, even in cases where it would be rather nice, such as here.