Gravitational fields aren't the issue here, only size matters for the 100D limit. Objects in the Oort cloud are too far apart to affect anything - you could draw a straight line through the Oort Cloud and it wouldn't intersect anything. They're separated by hundreds of millions of km, and their 100D limits of the vast majority are going to be under 100 km. Sure, a few are big enough to be "dwarf planet"-sized and those would have 100D limits of more like 100,000 km but that's still tiny compared to the space in between. (same applies to the asteroid belt too).
The only way you could go to a Oort Cloud object is to know exactly where it is and aim directly for it, you wouldn't just randomly be brought out of jump by hitting the 100D limit of one.
I can confirm that they're a VERY low percentage of the sky.
The probability of a stop due to Oort clouds, given 100 diameter limits, is P=0.0000816324338903662% or so. (I figured the average density given NASA numbers, then turned it into an average obscuration area per surface area of the oort...
For each 10x increase from 100D, 100x the chance.
T5.0 hop was 0.00816%, G stars blocked to 10 AU (jupiter)
T5.0 skip was 0.816%, G stars blocked to 100 AU (past neptune)
T5.0 Leap was 81.6%, G stars block to 1000 AU
T5.0 Bound, was automatically stopped. G stars block to 10,000 AU, or about 0.16 LY
T5.0 Vault was auto-stop oort, and G stars block 1.6 LY - essentially the system's starmap hex.
This is why 5.09 is not increased jump masking by type. Also note, At T5.0 Leap, a system within 2Pc of your line was likely to interrupt your Leap, and guaranteed to interrupt your bound, because the ~1 AU semi-major and semi-minor axis for outer bound are a series of almost always overlapping shadows when you try to look past.