The current main problem is that Qt often releases new modules under GPL and commercial only licenses. For example, the new Qt GRPC implementation and then it is all or nothing. Qt commercial would force us to essentially buy two licenses because we have a second app that acts as a third party dll loading app. These dlls often crash and thus we moved them into a dedicated app we could simply restart, but Qt license would force you two buy two licenses only because they talk to each other. So, no thank you Qt we will stick with LGPL for now, and move to something else in the future. See my blog post "Current Issues With The Qt Project - From The Outside Looking In" [1].
I think you have misunderstood the Qt licensing model when you say that you need two Qt licenses if you are building two separate applications?
The commercial licenses are a) per developer and b) per distributed device (if you distribute your software as part of a device), there is no per application licensing requirement.
> An application using Qt Commercial must not communicate with any another application using Qt LGPL-3.0 or Qt GPL, if both applications run on the same device. This is more restrictive than GPL.
The context there is "combining commercial and free open-source Qt licenses"; if you are using either commercial or open source licenses exclusively, there are no such restrictions.
[1] https://kelteseth.com/post/20-04-2023-current-issues-with-th...