It probably depends on how viable the app is without Touch-ID-only features.
Fully Viable Without Touch-ID
If an "average user" can get "full satisfaction" from the app without even realising there are extra features that are Touch-ID-only, then you probably want to remove the clutter and only show the features they have access to.
On first install you should probably tell them about the extra stuff available if they were to get a 'phone with Touch-ID; and you might have an item in the main menu (alongside things like Settings or About) that repeats the benefits of Touch-ID.
Usable Without Touch-ID (but not ideal)
If the app can be used without the Touch-ID-only features, but means users have to carefully pick their way around, or can only do half the things they would normally like/expect to do, then it is probably best to show the Touch-ID-only features (with suitable UI/UX elements so users know why they can't access them).
The main reason for showing the disabled options in the second case and not the first is to manage user-satisfaction/-expectation. For a "fully viable" app, a non-Touch-ID user can be completely happy with what they do have access to; they won't necessarily be "missing" the extra features, and consequently won't think less of the app for not offering them.
However, if an app is only "usable" without Touch-ID, a user is likely to be frustrated if there are no options for many of the things they want to do. Showing a disabled option for these things won't wipe out this frustration, but it will at least let them know that it's not because the writer of the app never thought such an option was needed, but because their 'phone lacks the ability to use it (but see note below).
- Not Usable Without Touch-ID
If the app essentially cannot be used without Touch-ID then there's no point users even installing it. If the app-store lets you, mark the app as requiring Touch-ID so it shouldn't even show up as available to users of 'phones without that feature.
Final Note: Although you say it is "as per client requirement" that certain features are Touch-ID-only, if at all possible I would push-back against that. My online banking app used to not support Touch-ID: certain operations had to be confirmed by entering a PIN or other such "old-school" measures. The app now has Touch-ID support and lets you use that (if you wish) in place of the old methods.
However, on a 'phone without Touch-ID, those old methods are all still available: everything that can be done with Touch-ID can still be done without it. (Also handy on a modern 'phone if your finger and/or the sensor is dirty/wet and Touch-ID is not working).