Direct3D 10 games are named correctly
DLSS5-Feeder 0.13.1-beta.1 added native support for 32-bit Direct3D 10 games — no dgVoodoo2, no DXVK — by creating a private D3D11 relay device inside the game process. Nothing in this tool ever blocked those games, but it described them as API unknown, assuming DX12, which is not a confidence-inspiring line to read before installing.
They are now detected and shown as DirectX 10 in the status line, the Games page and --check.
The detail that matters: a Direct3D 10 game imports d3d10_1.dll, not d3d10.dll. That is the same distinction that made the upstream installer classify Devil May Cry 4: Special Edition as a DirectX 9 game and set it up with dgVoodoo2, which cannot touch D3D10. Both names are matched here, and d3d11.dll / d3d12.dll still win when a game imports several.
Also: the refusal shown for a 32-bit DirectX 12 game now states what the add-on actually covers — Direct3D 9 (through dgVoodoo2), 10 and 11, but not 12.
Tested by unit test over import tables; I have no Direct3D 10 game installed to confirm an end-to-end install, so if you run one, a report is welcome.