Doing this would defeat the purpose of a persona completely.
What you are trying to do is to make an aggregated profile of a stakeholder group. This can be useful for some purposes, but is usually more work than it is worth. It is normally enough to identify each stakeholder group and its goals (including negative goals and fears). Any extraneous information will not help you build a better requirements specification.
The value of personas is to use it when communicating with team members who have little UX experience and cannot relate well to a description of stakeholders with goals and tasks. Making the persona portrait lifelike is what you absolutely need for this.
Example: you are making an application which allows students to enroll in courses. You could surely make a profile which says "student", and write down that a student is anybody from the first semester to the ones working on a graduate thesis. You could write a sentence which says "main goal: get X credits for the current semester". But your product owner, who works somewhere in the university administration, will not be able to do much with it, and will push for an interface fit for using by herself, which will probably have a very steep learning curve.
If you make a persona, you can have Dave, who just arrived at the university for his first semester in economics. He is bright, enthusiastic, eager to try out college life, but also a bit overwhelmed with the fact that mommy and daddy are not here to take care of things. He is also missing his sweetheart who will try to get accepted at the same university next year when she finishes highschool, but right now feels very far away. The introductory material suggested that he tries to get at least 10 credits towards microeconomics, 10 credits towards math and statistics, and to spread the remaining 10 between non-compulsory topics like business administration, or social science, or trade laws. But he wonders if this won't be a bit much and secretly hopes that it will be OK if he doesn't do any math the first semester.
So when your product owner insists on a screen which is structured in the same way as the paper forms she used to fill for students and send to the examinations bureau, you can tell her "I think this is too complicated for students", and she will probably say "They are at a university, they are supposed to be clever enough to fill out a simple form". But if she has read your persona, you can ask her "Do you think that Dave will know where to find the course booking number to fill in this field", she is much more likely to immediately understand that this won't end well, without you having to argue. She has probably seen hundreds of clueless Daves in her career; she just won't think of them when you say the generic "students", so you have to use the persona as the tool to prime her mental associations, and also kindle her empathy and compassion towards the user. The generic description will not work for that.
Aggregate stakeholder descriptions and personas are different tools for a UX specialist, each has its uses and has to look in a certain way in order to work. Create only one of them, or both, depending on whatever you need. But do not create a mix of them, and do not use one where the other would be appropriate.