It's a canned profile. Photoshop recognizes all the Intents and they behave largely as expected. S
I had looked at this at one time to get gamut and mapping info on the printer.
Here's the profile name and stats:
Profile: "C:\WINDOWS\System32\Spool\Drivers\Color\CNBBEMA0.ICM"
Descr: "Canon PRO-10 <GL><PP> 1/2 Photo Paper Plus Glossy&Gold" Version: 2.0.0 Copyright: "Copyright CANON INC. 2012 All Rights Reserved
RI->AI, WhitePoint L*a*b*: 93.9 -0.5 -2.5
RI->RI, WhitePoint L*a*b*: 99.7 0.0 0.0
PI->AI, WhitePoint L*a*b*: 93.7 -0.6 -2.4
PI->PI, WhitePoint L*a*b*: 99.5 -0.0 0.1
RI->AI, BlackPoint L*a*b*: 3.5 -0.1 -2.1
RI->RI, BlackPoint L*a*b*: 4.1 0.0 -2.1
RI->AI, BP Fr: L=4 L*a*b*: 5.3 -0.4 -2.2
RI->RI, BP Fr: L=4 L*a*b*: 6.2 -0.4 -2.1
PI->AI, BlackPoint L*a*b*: 3.5 -0.1 -2.1
PI->PI, BlackPoint L*a*b*: 4.1 0.0 -2.1
PI->AI, BP Fr: L=4 L*a*b*: 8.0 -0.7 -2.1
PI->PI, BP Fr: L=4 L*a*b*: 9.2 -0.6 -1.6
DeviceMax->RI L*a*b*: 100.0 0.0 0.0
DeviceMax->AI L*a*b*: 94.2 -0.6 -2.5
DeviceMin->RI L*a*b*: 4.1 0.0 -2.1
DeviceMin->AI L*a*b*: 3.5 -0.1 -2.1
The only thing really out of whack is the Perceptual intent reverse tables (A2B0). Perceptual should map black back to black. That is, incorporate BPC in both directions in the tables themselves. You will see the effect round-tripping to the printer profile and back to the working space RGB in Photoshop. Black comes back as L*=4.
There's also a small issue with the white point which should, in RI and PI map to device RGB (255,255,255). It actually maps to 253.6. I believe this to be due to some early confusion in V2 profiles about how the PCS values are to be interpreted and causes a slight shift, sub dE1. However, some CMMs recognize the different interpretations and will properly convert these. Photoshop does so not an issue at all with Photoshop.