What fixed issues with this for our codebase was simply running the lazyloading migration after migrating everything to standalone:

ng generate @angular/core:route-lazy-loading

See: https://angular.dev/reference/migrations/route-lazy-loading

It seems to amount to this: with standalone components NOT using lazyloading is no longer a viable route.