Out of all authors on that paper, most of them are experimentalists, but Krzysztof Pachucki is known as the "King of H2 calculations".
Three years after the paper you mentioned, Pachucki made the software freely available here. The abstract of the associated paper mentions that the paper provides benchmark results up to 18 digits, for example see this table of $\ce{H2}$ energies (it actually looks like the energies are converged even if rounded at the 19th or 20th digits):

In terms of RAM, the paper says:
"RAM: From several Mbytes to 512 Gbytes, depending on the size of the basis."
In terms of CPU time the paper says:
"Running time: From seconds to days, depending on the size of the basis."
But keep in mind that the paper is talking about converging to energy to 18+ a.u. digits in the most extreme cases, whereas the 2013 paper mentioned in your question is only talking about precision on the $10^{-4}$ cm$^{-1}$ scale, which means no more than 11 a.u. digits. So I would ignore the "512GB of RAM" and "days of CPU time" which are listed as the upper limits of the algorithm's cost, and I'd just focus on the lower limits which are "several MB of RAM" and "seconds of CPU time".
Also, the paper says:
"The parallelization of the calculation
of integrals in H2SOLV is almost 100% efficient, so that the evaluation time
is inversely proportional to the number of available cores (threads)."
So whatever the CPU time is, you can make it half of that by doubling the number of cores (something that's usually quite easy to do these days).
The one place where "CPU" appears in the paper is here:
"The computation time of H2SOLV with the input example specified above
is about a minute on a dual processor Intel Xeon CPU E5-2680 v3 2.50GHz."