Not had chance to try this, but as a suggestion, what about if you create a custom "Thread" configuration file that would have dummy values for the threading information but usable information for a downstream application, as an example a typical 1/4 threaded holes reads in the thread file as;
*1/4-20 UNC,20,0.207,2B,0.25,0.196,0.2175,2A,0.2489,0.1894,0.2164,1
in the following format
;; String *name;
;; Real pitch;
;; Real tapDrillDiameter;
;; String femaleClass
;; Real femaleMajorDiameter;
;; Real femaleMinorDiameter;
;; Real femalePitchDiameter
;; String maleClass
;; Real maleMajorDiameter;
;; Real maleMinorDiameter;
;; Real malePitchDiameter
;; Integer threadType;
;; 1 = UNC (units expressed as inches)
;; 2 = UNF (units expressed as inches)
;; 3 = UNEF (units expressed as inches)
;; 4 = UNS (units expressed as inches)
;; 5 = Metric Coarse (units expressed as millimeters)
;; 6 = Metric Fine (units expressed as millimeters)
;; 7 = Metric Special (units expressed as millimeters)
;; 9 = NPT (units expressed as inches)
;; 1000 = generic english (for user defined) (units expressed as inches)
;; 2000 = generic metric (for user defined) (units expressed as millimeters)
you could modify this to read as;-
1/4 Reamed,XXX,0.250,AA,.250,BBB,CCC,DD,EEEE,FFFF,GGGG,1000
this would create a 1/4in (.250 diameter hole) and you could use the other fields to carry additional data such as depth of ream etc., currently I am not sure whether this data can get "picked up" as parameters externally, however, the option may exist in the future. Furthermore, a spreadsheet maybe able to pick the details up from a lookup table that carries the same data.
Your other option maybe to create a series of catalog features based upon the hole and size information