I think the development team’s approach to creating generic airports is problematic because of this. This basically amounts to creating a fictional airport, and then attaching a label to it based on the closest-looking airport - in this case, Kannur.
The few things the real airport shares with the in-game fictional airport is the singular runway, the parallel taxiway, some taxiway exits (not in any order), and a passenger terminal adjacent to an apron. Using this logic, we can make the fictional airport we have and also call it “Thiruvananthapuram (TRV)” or “Thiruchirappalli (TRZ)” - both of them share the same features and operating modes and can be “represented” using this fictional airport.
Let me be clear: the layout should be the BARE MINIMUM. The point of generic airports is to speed up the airport creation process, and hence the time-consuming parts, which are modelling the surrounding buildings accurately, or detailing the stand layout lines, should be skipped. The textures do not need to be very accurate as well; focusing on the textures on the runway and the taxiways would defeat the point, once again. Skipping out on those details allows most of the development time to be focused on taxiing logic, which as the developers said, is the most time-consuming part of making an airport.
However, to blindly make a fictional airport and then associate it with a real life location is just not the way to do it in my opinion. The layout of an airport is fundamental to its identity; the positioning of the runway(s) and taxiways define the airport itself - almost no airports in real life are identical because of this, and you can always tell airports apart based on its shape.
I understand also that CNN is used to test winds, and to also test new features at future generic airports; the same could be achieved if the airport was modelled accurate to its real layout in the beginning. After all, they are operationally similar, and do use similar positions of exits when landing.
Fixing the layout would be a relatively difficult task because of this; the layout cannot be changed without spending massive amounts of time changing the taxiing logic. I therefore suggest the development team to do a location-based approach instead of a feature-based approach: pick a relatively high-demand, but under-represented location, and model the airport based on the location chosen. Even though the models are not going to be accurate, this approach still allows a good depiction of the chosen airport.