Currently, the internal cursor calls, such as history cursor, and metadata cursor, also go through the code path in the api macros. They need to call the api macros because they need the code in the api macros that manages the session frame. However, this makes them also being treated as a user api call, which is not ideal.

We should explore separating the functionalities of managing the api macros from the api macros and not calling the api macros in the internal cursor calls.

This ticket is to do some investigation and prototyping to explore its feasibility.