Hi Johannes,
the r2SCAN functional was developed using VASP and Turbomole. See
https://pubs.acs.org/doi/10.1021/acs.jpclett.0c02405 So the functionals named r2scan, r2scan-3c, etc. use this reference implementation. This is native code in Turbomole, but the implementation was done for up to first derivatives only. Hence, frequencies with aoforce cannot be calculated.
Later r2SCAN was also added to the libxc library, but including the 2nd derivatives. Functional names with the -libxc appendix are taken from the libxc library.
If the results are slightly different, then the libxc implementation deviates a bit from the original one - this is true for several functionals as libxc often uses a different number of digits for constants that are used in original implementations and papers (like pi or sqrt(pi), (3*pi^2)^2/3, ..). How large is the deviation?
Best Regards, Uwe