I believe the problem is with the converter, and not the display.
I don't think the TMDS clock is the problem. As I stated before, the TMDS clock mentioned in the output of moninfo.exe has a bug where it shows a default max TMDS clock of 165 MHz when the HDMI VSDB does not have enough bytes to actually specify a max TMDS clock.
I looked at the EDID of your BenQ BL3201PT again, trying to figure out where the 178 MHz might be coming from. The CE video identifier (VIC) that is marked as Native is 1920x1080p at 60 Hz. This has a CVT or GTF pixel clock of approximately 173 MHz (5 less than 178). Maybe that's a coincidence, because VIC #16 is supposed to be 148.5 MHz (CEA/EIA-861, not any of GTF, CVT, and CVT-RB; the latest standard is called CTA-861-G).
Did you test a direct DisplayPort (without converter) connection to the BenQ BL3201PT with the same resolutions and timings? This will prove that the limitation is with the converter and not your display. This problem is different than the 533/594 MHz problem that other displays have (because you're trying 2560 x 1440), but your display may have that problem as well if your display can't do 3840 x 2160 594 MHz without the converter).
I was able to do 2560 x 1440 up to 73 Hz (296 MHz) using the CMV-535 with Dell P2415Q. 74 Hz did not work (300 MHz). Using a direct DisplayPort connection, I can go up to 86 Hz, 350.81 MHz (but not 87 Hz, 355.06 MHz) which exceeds my display's max refresh rate of 76 Hz. I'm not sure why they differ. I previously reported my 3840 x 2160 tests where all refresh rates from 30 to 60 Hz worked with a direct DisplayPort connection, but the converter couldn't do the range between 35Hz and 44Hz (but did the ranges 30 to 34 and 45 to 60Hz). Very strange.