Yes, from the errors it looks like the module went through a migration path that skipped direct compatibility with your current setup.

What is happening is roughly this:

• • 1.0.0compatible with Mendix 10.24.x
  • 2.0.0currently marked for Mendix 11
  • but internally the package was last saved/opened in Mendix 9.24.12

Because of that, Mendix is asking for an intermediate upgrade path:

9.24.12 -> 10.21.x - 10.24.x -> 11.x

Mendix generally does not allow:

• direct import from incompatible higher versions
• or skipping required model upgrade ranges

So your understanding is mostly correct:

if the publisher did not release a proper Mendix 10-compatible intermediate version, upgrading becomes difficult/impossible directly.

What I would recommend:

• ask the module publisher to provide:
  • a Mendix 10 compatible release
  • or re-export/save the module properly in Mendix 11
• alternatively:
  • create a temporary app in the required intermediate version
  • import/open/save there
  • then migrate upward step-by-step

The confusing part here is that Marketplace compatibility metadata and the actual internal model version of the package are slightly mismatched.

Kindly mark this as the accepted answer if it helps.