I don't know it has as much to do with scale of the system vs the general architecture. E.g. the system I primarily work with these days has millions of lines but most PRs are for a small changes which are well contained in scope by the overall architecture.

reasonably you should already know what the code and project is supposed to do before they even start writing code, so you can get directional feedback in.

then you are maybe reviewing 1 out of 7 PRs that implement the agreed upon change

It's a cultural thing, but you can do incremental PRs towards a large goal. Giant PRs that are expected to be reviewed never really seemed worth it imho.