After I typed this, I came to realize that maybe you should just skip to the final paragraph, then if you want to, you can read the rest to see the rationale.
I have the new code up, and it certainly makes me rethink the premises of my original "outrageous" request. I see now that using all the categories complicates the problems immensely if we are trying to distinguish between poetry and prose; for example, a poem is categorized as creative writing, so when it is listed under creative writing, along with , say an essay, which is also creative writing, they both come off as prose, and we have no way to differentiate. I think that differentiation in that case is actually too complicated.
Another issue is that when the poetry category or any category listed in the array for slashes etc come up, the depiction in the final result comes out with the line-breaks in, so that the slash is not needed. To clarify: here is poetry correctly quoted with line breaks:
blah blah blah,
blah blah blah,
blah blah blah. . . no quotation marks, no slashes needed.
here is poetry correctly quoted without line breaks: "blah blah blah, / blah blah blah, / blah blah blah . . ." the slashes show the line breaks, which are needed because the line breaks are significant in poetry, unlike prose.
This is sort of like the use of the apostrophe. So many people misuse it that it is safer not to use it than to use it.
Conclusion: I really like the control over the number of words in prose that comes off really well. I like the way the actual poetry categories can be set to show the line breaks; I think if all entries showed line breaks, not just poetry, that would solve everything, and the slashes would not be needed. All one would have to do to make it work reasonably would be to reach a reasonable compromise between number of words and amount of poetry and prose one wants to show. So: no slashes, yes line breaks, yes word count. Does that make sense?