Hm, technically... yes

But :

You'd have to modify the .inf , so as to make the Driver Installer only install and register the raw Display driver in the System.

Glide and OpenGL would cause another Problem, as those Files would see 3 suitable rendering devices for their Renderdevice Init in such a configuration.
(with DirectX, you could always temporary disable unused Adapters using the integrated DXdiag Tool)

With OpenGL and Direct3D, I know there is the "AdapterNumber" that (if the Game's settings allow for manually selecting) can be used to choose between various 3D Adapters, not sure about Glide.

With OpenGL, there is also the possibility of a workaround, by again modiying the .inf of the Installer (or the OpenGL entry in the Windows Registry after Installation), and manually renaming the OpenGL core to something unique (e.g. 3dfxogl.dll becomes 3dfxv5gl.gll for the Voodoo5).

Otherwise, if a Game does not support handing over Init parameters, it would always choose the Primary Display adapter if possible.
That would mostly affect older Games, the most difficult being those that carry a native Glide support within their executables.

I don't think anyone has ever assembled such a "special purpose" Driver, so that would mean alot of manual Trial&Error work, with unknown outcome.

Worst case, you'd end up having to manually disable the Devices you don't want for rendering in the Device Manager as well...
---------
In a normal configuration, the Card that is installed last, will partly overwrite the previously installed Drivers and possibly replace its OpenGL Registry key.

The only way really would be to take the road of modifying the .inf of at least one Driver set, and rename all Driver files to a unique name. (that would still leave Glide with some trouble identifying the correct RenderDevice when initializing, OpenGL and Direct3D can be separated that way)

so after I concern with the Post from Falconfly also,
it seems to me the big Problem is to seperate the Cards from each other, especially in Dos, where the Device Manager-Disabling is naturally uneffectivley
Can it be that some Windows Games go around this and use a Card that is disabled in Windows ?

ps:I keep on testing the Utils (Powerstrip, Glidesweeper...)

exactly the Same Texture-Failures with 2 Cards, with their own and each other settings
Also tried a Tnt instead of the V5,but seems not to be the reason