I can’t tell you how many times a client has said to leave a field in the data model just in case they want to use it later.
Just don’t do it. Take it out now, if they want to use it later, then bring it in later. You can easily set up the app so that it is a super simple task down the road.
- Comment it out
- Use a drop field statement which they can remove later (suggested)
The thing is, if you are tuning an app that is already slow and having issues, you should not be thinking about future state. You should be thinking about getting what you currently have working to an acceptable level. Because you won’t be adding functionality to a clunky app if no one is using it because it take 3 minutes to load the page.