Read different sources saying different things. Ballast and Professional Practice both states the code research is not part of programming but Problem Seeking states that the more info you know upfront will help guide your decisions moving forward. Would it not make sense to review codes for a speculative project while doing programming research ?
This should be your hint. To answer yr question, Yes. (For example, knowing code defined-story/height limit will help your Stacking Diagram works better. Or Occupancy-A limit distance to Discharge will help Spatial Diagram works better, etc.)
Gang Chen examination questions also excludes zoning and codes form Programming:
17. Which of the following is not a part of architectural programming? Check the two that apply. a. Flunctional and operational requirements b. scoping c. decion-making processes d. codes and regulations e. geotechnical surveys
The answers are d and e.
23. Which of the following are essential elements for architectural programming? Check the three that apply. a. Topography b. project type c. goals and objectives d. quantitative requirements e. vegetation and wildlife f. zoning requirements.
I see the answer to your question as no. Programming, you are just gathering information about what the owner is looking for (eg. type of use, employees, owner wants bigger office space then manager, etc.). When you start looking at code and zoning at the programming stage, you are essentially designing (schematic design). You may be creating problems or looking for problems that does not exist at this stage.