Once the phone is unlocked, you can use TouchID as the phone is already open and you would not gain/lose anything from using TouchID in that scenario. But until the courts rule that you cannot be compelled to TouchID unlock your phone like a PIN, I think that is the safer route to take for now.
It's all about the threat model.
Keychain and NSFileManager have possible modes of "kSecAttrAccessibleAfterFirstUnlock" [0] and "NSFileProtectionCompleteUntilFirstUserAuthentication" [1] respectively that are (fittingly) in an open state within your app after you've unlocked the device.
[0]: https://developer.apple.com/reference/security/ksecattracces...
[1]: https://developer.apple.com/reference/foundation/nsfilemanag...
As an aside, I've found that, at least with my iPhone 5S, if my finger is wet (e.g. if I've licked it), it also is rejected.
That's why this https://support.apple.com/en-us/KM205083?cid=acs::applesearc... article states to contact them.
To frame the post and the conversation, I am targeting a loose but not universal threat model. If threat of deadly force is higher up in your risk scale than shoulder-surfing, or Apple cooperation is a given, then you might want to make very different choices, but more importantly, you probably need better advice than a blog post.
The only things I want to add are pair-locking, maybe a forced VPN profile, and a correction on how to check the Whatsapp fingerprint. You can find all these things in the Twitter thread.