CPQ Transaction Line Loop

We’re currently facing space constraints within the Pricing function and other objects. As part of our refactoring efforts, we had a question regarding best practices:

Would it be advisable to move the transaction line loop logic into a separate Commerce function and then invoke it from within the Pricing function?
We’re looking for guidance on whether this approach is recommended and aligns with CPQ best practices for performance, maintainability, and scalability.