Client connectivity in Exchange 2010 and 2016 co-existence

Hi Team,

i am in a transition of exchange 2010 to 2016.

I am currently looking at the client connectivity. I already followed: https://blogs.technet.microsoft.com/exchange/2015/10/26/client-connectivity-in-an-exchange-2016-coexistence-environment-with-exchange-2010/

I know that for the Activesync and Outlook anywhere which is currently published externally and loadbalanced to the E2K10 environment, has to be changed to the E2K16 environment as per the article.

However, i am more concerned about the internal outlook and other URL connectivities.

Should i repoint everything to the Exchange 2016 as well for internal connections? If yes, what should be done for the CAS array since there is none in Exchange 2016, should the cas array continue to point to the 2010 env or is it point to the E2K16 loadbalancer env. Please shed some light.