KOTOR/KOTOR II issues with ReShade 4

After working with ReShade 3.4.1, KOTOR I & II (OpenGL 1.4) stopped working for me on ReShade 4.0.0 and above. For ReShade 4 versions before 4.2.0, it crashes with something likeWith ReShade 4.2.0/4.2.1, it launches successfully, but many shaders cause the screen to go completely black.
Out of the ones I tested, AdaptiveSharpen.fx, Colorfulness.fx, Deband.fx, Denoise.fx, DPX.fx, FakeHDR.fx, FilmicPass.fx, Levels.fx, LumaSharpen.fx, SMAA.fx, Tonemap.fx, Vibrance.fx displayed this issue, while AmbientLight.fx, Bloom.fx, Curves.fx, DepthHaze.fx, DOF.fx, LUT.fx, MagicBloom.fx, MultiLUT.fx, MXAO.fx, ReflectiveBumpMapping.fx, Splitscreen.fx, UIMask.fx did not (though it should be noted MagicBloom is broken compared to 3.4.1, as its way overexposed compared to what it looked like there).
In case it could be a driver issue, my graphics card is an RX 580, on the latest drivers (19.4.3).

I can confirm this. After upgrading my computer, I can't play Reshade with Kotor 2 at all.

I saw the recent opengl related commits on the github and compiled to see if they fixed this issue, thankfully it does fix the black screen issue, but it seems the "broken" shaders are still broken. For example, SMAA does not work at all, with the edge texture showing pure black in statistics (and not showing at all when using the "view edges" option), displaydepth showing nothing (even though MXAO still works, weirdly it shows pure red for the depth tex in statistics despite working).

Is there anything that can be done on the application side to fix this issue, or is it something that has to be fixed on the shader end?

Tried 4.6.1 in KOTOR 1 and cannot reproduce issues. Started new game and SMAA works (albeit being limitied, because the game features some really heavy aliasing). Edge texture shows correctly too. Same thing with DisplayDepth, it shows depth correctly.