I don't use telepathy yet, sorry.
JogAmp APIs aren't to blame, we're not responsible for Intel's debatable choices and sometimes you have to tell your end users that they should use some hardware with more professional driver support. We spent several months in looking for some workarounds for the problem with some Intel GPUs no longer working under Windows 10 despite the fact that it's not caused by a bug in our APIs, we can't do more. We aren't responsible for driver bugs. Sometimes we succeed in writing some renderer quirks. We aren't responsible for your technical choices, I already wrote that Java Webstart doesn't help to work around some limitations and bugs.
Moreover, switching from Java3D 1.6 to Java3D 1.7 only requires to update the package names in your code, it's not an unachievable change.
Finally, I cannot fix bugs that aren't in our APIs and bugs that nobody reports. "we cannot ultimately migrate to 1.6 or 1.7 due to a number of problems" doesn't help at all and I still highly discourage the use of Java3D 1.5. Several contributors have worked in fixing bugs, sticking to Java3D 1.5 only to go on supporting a very few Intel GPUs or deprecated Java versions is a nonsense.