OK. In this case, you can directly specify the hole feature's name within the Item() call, instead of its Index Integer. Then, if it exists and the name is spelled correctly, it should recognize it and get it.
Also, I created a test part to test this code on my end, and determined that attempting to edit just the 'FastenerSize' string of the existing HoleClearanceInfo object won't work, but creating a new HoleClearanceInfo object, then setting that to the feature does work.
In case you weren't aware, there is a spreadsheet document within your Design Data\XLS\en-US\ folder (that last sub-folder will coincide with your installed language pack), called "clearance.xls". There is also another spreadsheet file in that folder called "thread.xls". When you use the Hole command to create either a clearance hole, or a threaded hole, it references the corresponding spreadsheet file for the available settings. When you want to specify a different setting, you have to make sure it matches something that exists within the spreadsheet.
This variation of the code specifies the hole feature by its name, then without checking what the hole feature's current fastener size is set to, it creates a new info object, with each setting set the way you want it, then sets that info object in place of the hole feature's current info object. This worked in my tests.
Dim oPDoc As PartDocument = ThisApplication.ActiveDocument
Dim oPDef As PartComponentDefinition = oPDoc.ComponentDefinition
Dim oHoleFeats As HoleFeatures = oPDef.Features.HoleFeatures
Dim oHole As HoleFeature = oHoleFeats.Item("LEFT SIDE FRONT FASCIA C-HOLE")
Dim oHCInfo As HoleClearanceInfo = oHoleFeats.CreateClearanceInfo("Ansi Unified Screw Threads", "Flat Head Machine Screw (82)", "#8", FastenerFitType.kNormalFitType)
oHole.ClearanceInfo = oHCInfo
If this solved your problem, or answered your question, please click ACCEPT SOLUTION.
Or, if this helped you, please click (LIKE or KUDOS) 👍.
If you want and have time, I would appreciate your Vote(s) for My IDEAS 💡or you can Explore My CONTRIBUTIONS
Wesley Crihfield

(Not an Autodesk Employee)