Thank you FJ. I have read and understand the published “how to” verbiage. Unfortunately, I’m left with a workaround that can be inconsistent. I know my general stroke count for 100 meters (35). I can therefore estimate my distance based on my manual count. To use my Apple Watch, I set my lap length to 1000 meters (equivalent to 350 strokes for me). The trick is to fool my watch that I’m making a turn after 350 strokes so that it will record 1 lap count. Basically, using the algorithm in the watch, I experiment with body movements that imply a turn (rotation on multiple axis), and then continue my swim. This works pretty well most of the time. I get accurate distance measurements, somewhat accurate stroke count, and the calorie burn and total time looks reasonable. But, occasionally, the watch detects subtle body part movements (hand, arm, trunk twist) and throws in another lap or stroke. Sometimes, I get outrageous stroke counts such as 54,000 instead of 350 for 1000 meters.
I suspect there is a growing number of tethered and infinity pool swim enthuseists such that I would love to see Apple enhance their swim tracking algorithms. In the meantime, I welcome other workaround ideas.