So your findings lead you to think there is a jar in oozie share lib directory that is taking precedence over yours?
Did you find which exact jar in oozie share lib directory is causing the problem?
I think the options you have tried are all good attempts to avoid jar conflict if that is coming from oozie. But perhaps the problem could come from MR configs as an example. Hence I suggest you try to find which jar could be causing the problem for you in this case.