<<Is it possible for a tinkerer with limited ability (like myself ) to implement this fix? >>
Yes.
Two different easy to use, but difficult to fully understand and configure, freeware air file editors are available from e.g.,
http://pagesperso-orange.fr/hsors/fsairfile.html
For this simple task Air Ed 1.52 is your best bet. The page says you need an updated aired.ini, but you won't to simply edit propwash effects. Leave all the files as they are and wherever you install the aired152 folder. Simply double click the supplied AirEd.exe, then navigate to and open the air file you are using. Then find and expand Record 1101.
Look down the long list of FD data fields in REC 1101 for Cn_dT Yaw Moment
What I believe to be the latest official version of the Stearman FD (FS04 PT-17 Ver 1.1.6 Apr 05) has this set to 0.002.
Look in REC 1 of the air file after you open it. If you are using a different air file the solution is 'likely' to be identical, but of course a different (unauthorised?) air file could have many problems.
Consider increasing the value incrementally until you can yaw the tail with fully deflected rudder into 'modest' propwash at very low taxi IAS with the stick held forward to unload the tail. If you overcook the value you will induce wild yaw authority at high thrust making co-ordinated turns in climbing flight and aerobatics harder to control; so only increase the value by just enough to solve the ground handling problem. Try increments of 0.005 and test each time.
If you define a personal key combination in FS9 (options/controls/assignemnts/Reload user aircraft) which causes air file reload you can then use that key combinbation after each edit and test each increment until you have just adequate yaw authority during very slow taxi. There 'should' be a higher value which makes differential braking irrelevant.
As you know the tailwheel animation may not behave as it would in real life whatever you code in the dynamics. Since the real Stearman had tailwheel steering (with disconnect to castor at unknown angle) I suggest that you implement that capability using no more than 45 degrees max in contact point.0 rather than implementing castoring and no tailwheel steering during your tests.
However......
Nothing you do will change the MDL tailwheel presence, so consider making point.0 a type 3 contact point = steel tipped skid.
point.0= 3, -17.3, 0, -6.2, 1200, 0, 0.3, max angle, 0.250, 2.5, 0.85, 0, 0, 0, 0, 0
Test whether defining it as a steel skid with both 0 and then 180 as max angle makes the dynamics behave more like a castoring tailwheel than actually defining the friction of that aft contact point as a rubber tyre.
The real Stearman had main wheel brakes. I still do not know if they could be applied differentially as delivered. That is not a given at the relevant date.
Remember the rear contact point has more friction with both cockpits occupied and yawing will require more RPM causing a larger turning circle. You should test on both grass and dirt, not just hard surfaces. Use MS default BGLs, not third party ones, during all FD ground handling tests.
Finally to all readers, please remember that many reported FD errors do not exist and the real problem is faulty user technique or expectation. Inexperienced tinkering with air files usually does more harm than good. The only reason I replied to this thread was that I believed the original question related to my original September 2003 FS9 update FD for this FS8 aircraft. I do not endorse generic air file tinkering by anyone who does not understand flight dyanamics.
FSAviator