I do recommend you use the latest version of the jasper plugin. The poi library used by the excel scope is shipped with the jasper plugin
and Servoy (used by the excel export plugin). So when you use an older Jasper plugin the version of the poi that comes with it might be different than the one Servoy ships with its core plugins. That could lead to unwanted results, because you and we have no influence to what is actually loaded (used) then. To add to that, the excel scope uses some additional libraries needed for xlsx (the ones in the poi directory). These should also match the poi core library.
So the whole fuss at the end is about that you want matching poi libraries in
plugins/jakarta-poi (jakarta-poi.jar, used by Servoy's excel plugin)
plugins/servoy_jasperreports (poi-xxx.jar used by the Jasper plugin)
plugins/poi (additional libraries for any poi.jar to support xslx)
To add to the confusion, different versions of the code in the excel scope work only with a matching library, because Apache tends to rename, deprecate and remove stuff in quite an agile way. And lastly, Servoy signs libraries (with a code signing certificate) and mixing Jasper, Servoy and POI may lead to different code signatures, because the signing certificate needs to be updated once in a while (happened last in 2019.12.1).
I hope that makes it all perfectly clear