Yeah, you cant expect modern frameworks to perform well on ancient hardware, its just not feasible. C, Delphi, etc are older and more performance optimized languages that work better on older machines to a degree.... Especially C++ and C.
Try running Windows 10 on spinning rust in a Core 2 Duo or Pentium 4 system and watch the pain unfold.
Java is a very heavy runtime and was always known to have severe performance penalties in the early days on now-ancient hardware when that hardware was current, Nowadays its fine because hardware has caught up in performance to run the slow bloat of Java itself.
Anyways, none of that has any correlation to B4X, and as Erel said, B4X changes wont affect anything. That is all Java.
As languages become more abstracted away from their hardware and dependencies on runtimes and libraries increases, performance penalty will increase with it due to the amount of excess code that has to be run to do translation back down to the hardware level, plus the memory management/garbage collector code, etc. etc. VB6 was pokey on older hardware too for this reason while native C was super fast.
The more layers there are on top, the longer it takes you to get back down to the bottom... The solution? dig down faster! (thats how i see computing anymore)