You are right, that makes a call down into the engine. I don't really understand what your additional parameter would do, but the engine would need to be enhanced to support it, unless you can make a wrapper utility function that works with the engine code as it is and then adjust the result per your additional parameter. You should document what you are looking for here and our moderators can help make sure the appropriate product teams see it.
Thanks for your response Mike. There has been some discussions that has happened internally with the BA's and currently we are fine in using the existing function with the same number of parameters that the current Utility function supports. In future if they come back again with additional parameters I would be sharing the document with the requirement that we are looking for.