I'd say the answer is no, you cannot do that.
Problems whose root-cause is related to the time passed since the last reboot are not unusual. But there is not just one reason why such problems happen, and consequently there is not one single setting you can change to reproduce the problem.
An operating system has a number of counters that will increase while the system is running. Some are directly proportional to the time gone by, others are driver by other events.
Even if you managed to change one value to make it look as if the system had been running for a long time, the problem may be related to another value, which you did not change.
Such counters may reset due to certain conditions. Many will start from zero after a reboot, but they may also start over from zero for other reasons. Another reason for a counter to start over from zero would be if it reaches a maximum value. There can be bugs which will cause problems when such a counter overflows.
But to debug the problem you need to know a bit more about what is triggering it than just "because the server hadn't restarted for a long time"