I will take you at your word when you say you are "ready" to implement this, but there are good reasons you aren't finding source code lying around.
Aside from the complexity, a "practical problem with PTAS is that the exponent of the polynomial could increase dramatically as ε shrinks, for example if the runtime is O(n(1/ε)!)." This leads to even more rigid requirements like EPTAS and FPTAS, although I don't believe TSP currently has solutions at these stricter requirements. So bear in mind that a PTAS solution doesn't necessarily eliminate wide variability as you vary the approximation parameter.
The most applicable paper I've found to your post is An Empirical Analysis of Approximation Algorithms for Euclidean TSP .
An innovative Polynomial-Time Approximation Scheme (PTAS) for the
Euclidean TSP was given by Sanjeev Arora. To date, there is no
evidence that it can be implemented to be practically useful. In light
of this, we propose an implementation of the Euclidean TSP that is
based on the essential steps of the Arora’s PTAS and adds some
heuristics to improve the running time.
The authors do not provide a link to their C++ implementation but you could try emailing them. The more important aspect of their paper is the quantitative comparisons they made of their Arora-based approach vs. 4 other competitive algorithms provided in the Concorde solver. Their paper concludes:
Experimental results show that Arora´s PTAS is practically feasible.
Table I and Table II show that in spite of its good performance, it
seems that our approach must be improved to generate more approximate
solutions. In most cases the significant theoretical results are lost
due to implementation decisions. We think the quality of the solutions
had to do with implementation aspects linked to data structures and
the need to give more hints about which portals must be used by the
tour.
If you read their paper in detail, you will see they made various implementation decisions and optimizations, many of which are likely sub-optimal and/or not rigorously justified. Read the results for yourself, but it seems to me that their PTAS algorithm completed in 0.25x to 1.0x the time of the other algorithms on average, but the results were sometimes substantially worse. It seems to me the biggest risk here is the "implementation decisions" and heuristics you may need to trial-and-error in hopes of actually realizing those elusive performance benefits.