The implementation I've added fixes the ITL overscan size by setting it to 64 pixels. I did not extend it to cover the doubly-overscanned region, as the current ip_isr overscan code automatically does extension when doParallelOverscan is enabled.
The main goal of this fix was to remove the log messages that are sometimes confusing. In addition, I removed another log message that would trigger for every assembly, as the header DETSEC and the values in the cameraGeom object disagree.
Finally, to ensure consistent processing of obs_lsst data, I've made the MEDIAN_PER_ROW overscan correction the default. This is widely acknowledged as the current best, and having it not be the default has created a number of confusing results that were traced back to overscan fit mismatch.