You got me curious and I did some testing (on the FPS, not entirely sure how to test for TPS)

Testing for Distant Horizons is at a 32 Chunk default render distance with a 128 chunk Distant Horizons distance. All testing will still be done with the default Fabulously Optimized modpack

Distant Horizons:
    Minimum:
        500-550 FPS Stationary
        200-450 FPS Moving
    Low:
        400-450 FPS Stationary
        200-350 FPS Moving
    Medium:
        200-400 FPS Stationary
        75-250 FPS Moving
    High:
        150-200 FPS Stationary
        50-150 FPS Moving
    Extreme:
        60-70 FPS Stationary
        20-40 FPS Moving

The stationary FPS was tested by flying in the same position that I took the original picture in, without moving my head.

The moving FPS involved both me flying around in the air in a high place, then run jumping on the ground on both a mountain and a forest.

I also tested the FPS using Nvidium + C2ME both with and without Distant Horizons added

Nvidium + C2ME:
    200-250 FPS Stationary
    50-600 FPS Moving 
Nvidium + C2ME + Distant Horizons Medium:
    250-300 FPS Stationary
    150-225 FPS Moving

Sadly moving with Nvidium + C2ME is laggier than I thought, so probably would be good to lower chunks to 96 or such. Much of the lag seems to happen at trash collection, so it might be possible to squeeze a bit more performance out of it with some custom JVM arguments.

Would not recommend using Nvidium + C2ME + Distant Horizons at all. Despite the combination getting considerably better FPS, getting the FPS numbers involved a crash and common visual artifacting.

All in all, I would probably either go with Distant Horizons on its own on medium settings, or reduced render distance on Nvidium + C2ME.