I suggest you follow Bernhards advice first:
You did read the license coming with the dll? It is a plain LGPL.
What it says there in short is the following:
You're free to use the library as it is. So if u just link to the dll and use it like that, in other words: just reference it without any modification or without importing the code directly, you can use it at will. No name changes are allowed here (fairly obvious, because that's a modification).
If, on the other hand, you modify the dll in any way, you're obliged to publish the modificated dll (including sourcecode and license!!!) under the same license as the original. To spell it out: the modificated dll and the new sourcecode fall under the LGPL in that case.
That goes too for any derived work based on the code in the dll. So when u use the sourcecode of the dll inside in another application, or parts of it, or any modification based on that code, the application becomes a derived work. In other words: you're obliged to publish that application (again, including sourcecode and license) under the LGPL.
Failing to do so is breaking the license, which is protected by copyright laws. Those have a strong legislation history in almost any country, so I advice you NOT to attempt that. After all, if a company like IBM releases under the LGPL, you can bet it's a reliable and well-protected license.
I can't help u with the working of the dll under another name. But that's easely checked: link to it from a demo application and try it out. Quite frankly why it's so important to change the name is beyond me. But beware: if it does then your application has to be published under the LGPL. And maybe it's just a hunch, but I feel that's not exactly what u want.
I may be off a little bit on the details (after all, I'm no lawyer), but the guidelines above shouldn't bring you into trouble. Better to be safe than sorry. I hope your questions are answered now.
PS.: if I'm really off I'd like to be corrected off course.