Oh hoo boy ... perhaps an improper data range levels also. Sheesh.
Understand, I work for/with/teach pro colorists, and am around intensely, highly detailed discussions on color depth/volume/space/math/handling/hardware constantly. Where going way down the rabbit hole is necessary to get full understanding of what happens under the hood.
YUV Rec.709 media ... technically Y/Cb-Cr ... is by the standards supposed to be encoded in Limited/Data range. Only 12 bit RGB Rec.709 ... made by very few cameras ... is supposed to be encoded as full range.
Whether it is encoded as full or limited, the same number of 'levels' is recorded to the file, they are simply encoded differently. And monitors are set to automatically handle the display correctly showing both 0-255. IF you don't muck up the GPU or monitor settings.
That is very confusing and is a major issue for quite a few folks who's cameras allow setting YUV media to 'full'. WRONG. You don't get anything more into the file, you do run into problems in editing and playback.
I've had to help several people, across both Premiere and Resolve, sort things out so with the files they've already produced they could get predictable behavior in exports that worked normally. And for some, who shot their own clips, chose to set the camera correctly to limited to avoid problems.
But others got this from the client or the shooter the client hired and just needed to know how to fix it so it worked right. There are Lumetri presets in the Presets bin for full->limited conversion. That fixes it for working within Premiere, and the export will be properly limited range.
So you stepped into a hot-button for me there ... sorry, but it's something that is a pain in the patootie.
I'll try to download that LUT today and see if Premiere sees it on my system. Not all LUTs are the same, by the way. Some LUTs have different structures to them. And can be used with X an Y software but not with Z or Q. Driving colorists nuts, of course. One of many reasons to get away from LUT-based workflows, and to using the safer algorithmic processes now in both Premiere and Resolve. Although neither supports all cameras for algo conversions. Sadly.
Some of the Resolve LUTs cannot be seen or used by Premiere, for instance. I've been able to take them into LutCalc, and re-export them to a more standard cube at need. So far.
I downloaded the whole group of folders from your Canon link, put several from each 1D and 3D sets, in:
Program Files/Adobe/Common/Luts/Creative
And I was able to access and apply all of the seven or so from the Creative tab dropdown slot.
Puzzling, why doesn't that work on your end? Huh.