There are several problems with the MTQ Operator:

Namespace Locking: While it functions, bugginess has been observed in the wild.
Tightly coupled with KubeVirt Code: One-to-one changes are required for updates to logic in either repository.
Modifies the quota set by the cluster admin.
Accounting nuances: Both source and target pods are counted until migration completes.

The AAQ Operator resolves all these issues; therefore, the MTQ should be dropped, and we should fully commit to the AAQ Operator.