Why about trying to get this driver working on top of current ntdll ? All drivers accesses should pass by kernel calls no ?
In the perfect world, yes.. but this is not how most copy protections do it.
Using the copy protection's driver directly will IMHO not be possible without emulating certain things for the driver and this is probably also illegal in respect to the DMCA. (lying to the kernel mode driver is kind of the same as lying to the user-mode part of the protection, no?!)
If it should be true (sure that it isn't ;), i don't know why ms doesn't includes secdrv.sys in the core, and calls it from ntdll, what should be the end of wine running native applications ;)
Regards, Carlos.