UWP/COM Component Extension Worthwhile?

[Mark out West (markfling)]

In my free time I've been busy writing a UWP component library extension to ESENT.DLL for a few months now. It's a fairly direct translation to and from the WinRT/UWP ABI into the ESE API, objectifying things such as ESE/JET instance, session, table/cursor, and index handles into ref-counted wrapped components all derived from IInspectable. I selected the C++/WRL for the development framework to keep it close to the metal as possible.

Now with this release of the ESE source, I'm wondering if a natively-implemented UWP component library would be worth releasing into GitHub as a sub-effort to this project. An initial port of the code would simply call through the existing Jet/ESE API implemented via "jetapi.cxx" within the ESE codebase as a separate component library (e.g., "eseuwp.dll"). Later on a better implementation might be via direct calls into the internal ESE functions, but this would require integration into the original esent.dll library.

Worthwhile? Waste of time? Comments? Suggestions? Insults?