But accessing lists after they were filled with FetchEager will not trigger additional Requests later on, as my tests are showing.
Yes, there are several SQLs triggered, but before your changes of october, accessing list properties, that should have been fetched by FetchEager triggered these List-Statements again, so that these were fired several times, because Proxy.Loaded was false