This is of course correct. But, only with some qualifiers. For starters, this extra information, such as variable and/or value labels, only exists in the variable-level metadata on the Dataverse side for *some* tabular files, depending on the format of the original ingested file. For example, here at our own production Dataverse, something like 70% of all the recently created tab. files were ingested from CSV. Therefore none of these have any labels or categorical values - or anything really except for the variable names and guessed types; so there's nothing extra to preserve in an RData frame.
If the original was Stata (our second most popular format here) - the R user can have all the extra labels and such preserved by downloading the .dta original and importing it into R directly. R has excellent Stata import support via the package "foreign". (As a matter of fact, when Dataverse serves download-as-RData for a tab. file with a Stata original, that's exactly what it does behind the scenes - it makes R import the .dta and save it as an R frame!).
If the original was RData itself... then the whole point is moot.
So this only leaves SPSS as a rich ingestable format that could benefit from having any extra metadata preserved in an RData frame - and how many people are still using SPSS, really? (that was a non-rhetorical question btw; I know we have fewer and fewer SPSS files uploaded here - but I'm assuming it could be different at other installations - ?).
But then, whatever value this potentially provides, having these SPSS labels and categories preserved in an R file, it is a bit outweighed by the fact that the whole subsystem is just unreliable and flaky, and works on some files but not on others, unpredictably. We use some rather messy R code, to try to convert categorical variables into R factors with proper labels... but messy it is and none of the current core developers are brave enough to attempt to work on it...
All that said, I personally didn't feel it was necessary to retire this service until recently. I felt like flaky as it was, it wasn't hurting really, and it was providing something useful for at least a few files. But then this has been subject of some lively debate (in GitHub issues and elsewhere), and we've had some users explicitly ask us to drop it.
I would happily agree that a good alternative to retiring this service would be improving it, making it more reliable, updating the R components behind it and making it produce better and more useful R data frames... (and for those who actively dislike the idea of their Dataverse instances serving RData, for whatever reason, we could just make it easy to disable, optionally). But, this effort would need to come from the community. Because the core team has no resources to invest into it.
Best,
-L.A.