I checked the code and we do cache the query plan to use for loading the entity graph that is affected by MERGE cascading, so this is all intentional.
If you don’t want any cascading to happen, how about you try using the StatelessSession API?